SlideShare una empresa de Scribd logo
1 de 25
Descargar para leer sin conexión
Postcards from the Agile Frontier,[object Object],IIBA Meeting,[object Object],March 3, 2010,[object Object],Elena Yatzeck,[object Object]
Agenda,[object Object]
Agenda,[object Object]
Agile Basics,[object Object],For purposes of this presentation, “agile” means an iterative software development process based on the Agile Manifesto, drafted in 2001 and signed by a set of people who have gone on to define significant additional details since then.,[object Object],Agile Manifesto,[object Object],	We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: ,[object Object],	Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan ,[object Object],	That is, while there is value in the items on the right, we value the items on the left more. ,[object Object],	Kent Beck, Mike Beedle, Arie van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler, James Grenning,JimHighsmith, Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick, Robert C. Martin, Steve Mellor, Ken Schwaber, Jeff Sutherland, Dave Thomas,[object Object],Visit:  http://agilemanifesto.org/ for more!,[object Object]
Obligitory Blurry Photo of Manifesto Signers,[object Object],5,[object Object]
Sample Agile Process (Scrum),[object Object],6,[object Object]
Full Project:  the Agile Difference,[object Object],7,[object Object]
Why is Agile Popular?,[object Object]
Agile Artifacts,[object Object]
Agenda,[object Object]
Classic Agile Roles,[object Object]
Where does the BA fit in?,[object Object]
Two Helpful Facts To Know,[object Object],Classic Agile “simplifies” by removing the BA role from the roster.,[object Object],Actual Agile Projects of Any Scale Always Use Business Analysts,[object Object],Standard role at ThoughtWorks (their roles are:  PM, BA, Dev, and Test),[object Object],Standard in WBS illustration used by Rally SCM trainers,[object Object],Standard in most classic texts on “Agile at Scale”,[object Object]
Agile BA Roles Attempted at NAVTEQ,[object Object],Role 1:  Business Analyst,[object Object],Role 2:  Part of 4-Headed Product Owner Team,[object Object],Role 3:  Representative for Product Owner (“Product Proxy”),[object Object],Role 4:  Scrum Master,[object Object],Role 5:  Tester/QA (not tried, but we’re intending to),[object Object]
Role 1:  Business Analyst,[object Object]
Agile Artifacts at Scale,[object Object]
Role 2:  Part of “Product Owner Team”,[object Object]
Role 3:  Representative for Product Owner (“Product Proxy”) ,[object Object],At NAVTEQ, Product Management is not available for daily scrum,[object Object],For our 2010 Pilots, we have created a “Product Proxy” role,[object Object],PO is available at product inception, and for start and end of sprints,[object Object],PP is 100% dedicated, and stays in frequent contact with PO,[object Object]
Role 4:  Scrum Master,[object Object],Ferry versus Bridge,[object Object],Fowler describes the relationship between business and technology as the “Yawning Crevasse of Doom”,[object Object],The traditional BA might be described as building a ferry (over the crevasse) between business and technology through written requirements,[object Object],Fundamentally, the SCM is a person presiding over a process which builds a permanent bridge over that chasm—same function, different technique,[object Object]
Role 5:  Tester/QA Role,[object Object],“Post-Agile” Techniques Include:,[object Object],Test Driven Development,[object Object],User Acceptance Test Driven Development,[object Object],At simplest:,[object Object],BAs write unit, system, and user acceptance criteria for each story, and QA approves,[object Object],BA/QA role melds:  the user acceptance criteria IS the requirement set,[object Object],BA/QA/Dev role melds:  automated testing tools allow the requirements to be actually encoded as part of the code base.  BA/QA/Dev are all able to do this tool-based encoding.,[object Object]
What You Found,[object Object],…what has worked at your company?,[object Object]
Agenda,[object Object]
The Bottom Line,[object Object],First principle of the Agile Manifesto:  We Value…“Individuals and interactions over processes and tools”,[object Object],In our experience, the BA is often the individual who makes a project make sense.,[object Object],That is not going away!,[object Object]
Three Classics for More Reading,[object Object],Agile Project Management: Creating Innovative Products (2nd Edition) by James A. Highsmith (Paperback - July 20, 2009).,[object Object],Agile Project Management with Scrum (Microsoft Professional) by Ken Schwaber (Paperback - Feb. 11, 2004),[object Object],Agile Software Development: The Cooperative Game (2nd Edition) by Alistair Cockburn (Paperback - Oct. 29, 2006),[object Object]
About Elena,[object Object],Elena Yatzeck is Director of Software Specifications within the Architecture and Software Engineering group at NAVTEQ.  She has 25+ years of experience in IT software engineering, mostly in the education and digital data industries.,[object Object],Elena is PMP and Scrum Master certified.  A Phi Beta Kappa graduate of Dartmouth College, she earned her MA and PhD at the University of Chicago, as well as completing 8 of 20 courses towards her MBA at the Chicago Booth School of Management.,[object Object],Reach her at eyatzeck@gmail.com  ,[object Object]

Más contenido relacionado

La actualidad más candente

Tdd 4 everyone full version
Tdd 4 everyone full versionTdd 4 everyone full version
Tdd 4 everyone full versionLior Israel
 
The five expertise of a software architect
The five expertise of a software architectThe five expertise of a software architect
The five expertise of a software architectLior Bar-On
 
Taming Big Balls of Mud with Diligence, Agile Practices, and Hard Work
Taming Big Balls of Mud with Diligence, Agile Practices, and Hard WorkTaming Big Balls of Mud with Diligence, Agile Practices, and Hard Work
Taming Big Balls of Mud with Diligence, Agile Practices, and Hard WorkJoseph Yoder
 
Introduction to bdd
Introduction to bddIntroduction to bdd
Introduction to bddSeb Rose
 
My Career Journey: An Unconventional Path into DevOps
My Career Journey: An Unconventional Path into DevOpsMy Career Journey: An Unconventional Path into DevOps
My Career Journey: An Unconventional Path into DevOpsVMware Tanzu
 
The Role of the Software Architect (short version)
The Role of the Software Architect (short version)The Role of the Software Architect (short version)
The Role of the Software Architect (short version)Hayim Makabee
 
Best Practices in Process Automation - Chapter 1
Best Practices in Process Automation - Chapter 1Best Practices in Process Automation - Chapter 1
Best Practices in Process Automation - Chapter 1Bonitasoft
 
User story estimation with agile architectures
User story estimation with agile architecturesUser story estimation with agile architectures
User story estimation with agile architecturesRaffaele Garofalo
 
Software Craftsmanship VS Software Engineering
Software Craftsmanship VS Software EngineeringSoftware Craftsmanship VS Software Engineering
Software Craftsmanship VS Software EngineeringAndy Maleh
 
Software Craftsmanship - It's an Imperative
Software Craftsmanship - It's an ImperativeSoftware Craftsmanship - It's an Imperative
Software Craftsmanship - It's an ImperativeFadi Stephan
 
Agile Development Ultimate Slides
Agile Development Ultimate SlidesAgile Development Ultimate Slides
Agile Development Ultimate Slidesgilashikwa
 
Clean Software Design - DevNot Summit Istanbul 2017
Clean Software Design - DevNot Summit Istanbul 2017Clean Software Design - DevNot Summit Istanbul 2017
Clean Software Design - DevNot Summit Istanbul 2017Lemi Orhan Ergin
 
Waste Driven Development - Agile Coaching Serbia Meetup
Waste Driven Development - Agile Coaching Serbia MeetupWaste Driven Development - Agile Coaching Serbia Meetup
Waste Driven Development - Agile Coaching Serbia MeetupLemi Orhan Ergin
 
Agile Project and Portfolio Management Using Jira - AgileSolutions
Agile Project and Portfolio Management Using Jira - AgileSolutionsAgile Project and Portfolio Management Using Jira - AgileSolutions
Agile Project and Portfolio Management Using Jira - AgileSolutionsKeith Klundt
 
BDD in Action – principles, practices and real-world application
BDD in Action – principles, practices and real-world applicationBDD in Action – principles, practices and real-world application
BDD in Action – principles, practices and real-world applicationJohn Ferguson Smart Limited
 
In Search Of An Agile Documentation Process
In Search Of An Agile Documentation ProcessIn Search Of An Agile Documentation Process
In Search Of An Agile Documentation ProcessSusan Patch
 
Saf08 Growing Architects Kevin Francis
Saf08 Growing Architects   Kevin FrancisSaf08 Growing Architects   Kevin Francis
Saf08 Growing Architects Kevin FrancisKevin Francis
 
Way to Agile from Tradition - Agile Way
Way to Agile from Tradition - Agile WayWay to Agile from Tradition - Agile Way
Way to Agile from Tradition - Agile WayRamadevi Lakshmanan
 
Lean Enterprise Architecture
Lean Enterprise ArchitectureLean Enterprise Architecture
Lean Enterprise ArchitectureExcella
 

La actualidad más candente (20)

Tdd 4 everyone full version
Tdd 4 everyone full versionTdd 4 everyone full version
Tdd 4 everyone full version
 
The five expertise of a software architect
The five expertise of a software architectThe five expertise of a software architect
The five expertise of a software architect
 
Taming Big Balls of Mud with Diligence, Agile Practices, and Hard Work
Taming Big Balls of Mud with Diligence, Agile Practices, and Hard WorkTaming Big Balls of Mud with Diligence, Agile Practices, and Hard Work
Taming Big Balls of Mud with Diligence, Agile Practices, and Hard Work
 
Introduction to bdd
Introduction to bddIntroduction to bdd
Introduction to bdd
 
My Career Journey: An Unconventional Path into DevOps
My Career Journey: An Unconventional Path into DevOpsMy Career Journey: An Unconventional Path into DevOps
My Career Journey: An Unconventional Path into DevOps
 
The Role of the Software Architect (short version)
The Role of the Software Architect (short version)The Role of the Software Architect (short version)
The Role of the Software Architect (short version)
 
Best Practices in Process Automation - Chapter 1
Best Practices in Process Automation - Chapter 1Best Practices in Process Automation - Chapter 1
Best Practices in Process Automation - Chapter 1
 
User story estimation with agile architectures
User story estimation with agile architecturesUser story estimation with agile architectures
User story estimation with agile architectures
 
Software Craftsmanship VS Software Engineering
Software Craftsmanship VS Software EngineeringSoftware Craftsmanship VS Software Engineering
Software Craftsmanship VS Software Engineering
 
Software Craftsmanship - It's an Imperative
Software Craftsmanship - It's an ImperativeSoftware Craftsmanship - It's an Imperative
Software Craftsmanship - It's an Imperative
 
.NET Career Direction
.NET Career Direction.NET Career Direction
.NET Career Direction
 
Agile Development Ultimate Slides
Agile Development Ultimate SlidesAgile Development Ultimate Slides
Agile Development Ultimate Slides
 
Clean Software Design - DevNot Summit Istanbul 2017
Clean Software Design - DevNot Summit Istanbul 2017Clean Software Design - DevNot Summit Istanbul 2017
Clean Software Design - DevNot Summit Istanbul 2017
 
Waste Driven Development - Agile Coaching Serbia Meetup
Waste Driven Development - Agile Coaching Serbia MeetupWaste Driven Development - Agile Coaching Serbia Meetup
Waste Driven Development - Agile Coaching Serbia Meetup
 
Agile Project and Portfolio Management Using Jira - AgileSolutions
Agile Project and Portfolio Management Using Jira - AgileSolutionsAgile Project and Portfolio Management Using Jira - AgileSolutions
Agile Project and Portfolio Management Using Jira - AgileSolutions
 
BDD in Action – principles, practices and real-world application
BDD in Action – principles, practices and real-world applicationBDD in Action – principles, practices and real-world application
BDD in Action – principles, practices and real-world application
 
In Search Of An Agile Documentation Process
In Search Of An Agile Documentation ProcessIn Search Of An Agile Documentation Process
In Search Of An Agile Documentation Process
 
Saf08 Growing Architects Kevin Francis
Saf08 Growing Architects   Kevin FrancisSaf08 Growing Architects   Kevin Francis
Saf08 Growing Architects Kevin Francis
 
Way to Agile from Tradition - Agile Way
Way to Agile from Tradition - Agile WayWay to Agile from Tradition - Agile Way
Way to Agile from Tradition - Agile Way
 
Lean Enterprise Architecture
Lean Enterprise ArchitectureLean Enterprise Architecture
Lean Enterprise Architecture
 

Similar a Postcards From The Agile Frontier Final

SCA in an Agile World | June 2010
SCA in an Agile World | June 2010SCA in an Agile World | June 2010
SCA in an Agile World | June 2010Klocwork
 
An Agile Development Primer
An Agile Development PrimerAn Agile Development Primer
An Agile Development PrimerDerek Winter
 
Agile intro resources
Agile intro resourcesAgile intro resources
Agile intro resourcesAnwar Sadat
 
Case Study - Distributed Scrum Development V2
Case Study -  Distributed Scrum Development V2Case Study -  Distributed Scrum Development V2
Case Study - Distributed Scrum Development V2Jonathan Chashper
 
Why Agile? Why Now? IPMA Forum 2009
Why Agile? Why Now?   IPMA Forum 2009Why Agile? Why Now?   IPMA Forum 2009
Why Agile? Why Now? IPMA Forum 2009skipangel
 
Agile Software Architecture
Agile Software ArchitectureAgile Software Architecture
Agile Software ArchitectureChris F Carroll
 
The Four Characteristics Of The Agile Traditional Software...
The Four Characteristics Of The Agile Traditional Software...The Four Characteristics Of The Agile Traditional Software...
The Four Characteristics Of The Agile Traditional Software...Serena Brown
 
Agile Injection, Varberg
Agile Injection, VarbergAgile Injection, Varberg
Agile Injection, VarbergFredrik Wendt
 
Agile Development with Scrum.pptx
Agile Development with Scrum.pptxAgile Development with Scrum.pptx
Agile Development with Scrum.pptxzuma14
 
Session 14 2 Introducing Scrum At
Session 14 2 Introducing Scrum AtSession 14 2 Introducing Scrum At
Session 14 2 Introducing Scrum AtKim Moore
 
The Role of a BA on a Scrum Team IIBA Presentation 2010
The Role of a BA on a Scrum Team IIBA Presentation 2010The Role of a BA on a Scrum Team IIBA Presentation 2010
The Role of a BA on a Scrum Team IIBA Presentation 2010scrummasternz
 
Managing Agile Software Development Projects
Managing Agile Software Development ProjectsManaging Agile Software Development Projects
Managing Agile Software Development ProjectsMartina Šimičić
 
Introduction to Software Engineering
Introduction to Software EngineeringIntroduction to Software Engineering
Introduction to Software EngineeringSibel Kuzgun AKIN
 
Agile Overview As V1.2
Agile Overview As V1.2Agile Overview As V1.2
Agile Overview As V1.2Anjan Roy
 
Business Analyst As Product Owner
Business Analyst As Product OwnerBusiness Analyst As Product Owner
Business Analyst As Product OwnerCraig Brown
 
Software Craftsmanship
Software CraftsmanshipSoftware Craftsmanship
Software CraftsmanshipMike Clement
 

Similar a Postcards From The Agile Frontier Final (20)

Agile Engineering Practices
Agile Engineering PracticesAgile Engineering Practices
Agile Engineering Practices
 
SCA in an Agile World | June 2010
SCA in an Agile World | June 2010SCA in an Agile World | June 2010
SCA in an Agile World | June 2010
 
An Agile Development Primer
An Agile Development PrimerAn Agile Development Primer
An Agile Development Primer
 
Agile intro resources
Agile intro resourcesAgile intro resources
Agile intro resources
 
Case Study - Distributed Scrum Development V2
Case Study -  Distributed Scrum Development V2Case Study -  Distributed Scrum Development V2
Case Study - Distributed Scrum Development V2
 
Why Agile? Why Now? IPMA Forum 2009
Why Agile? Why Now?   IPMA Forum 2009Why Agile? Why Now?   IPMA Forum 2009
Why Agile? Why Now? IPMA Forum 2009
 
Agile Software Architecture
Agile Software ArchitectureAgile Software Architecture
Agile Software Architecture
 
The Four Characteristics Of The Agile Traditional Software...
The Four Characteristics Of The Agile Traditional Software...The Four Characteristics Of The Agile Traditional Software...
The Four Characteristics Of The Agile Traditional Software...
 
Agile Injection, Varberg
Agile Injection, VarbergAgile Injection, Varberg
Agile Injection, Varberg
 
Software engineering in the agile manifesto
Software engineering in the agile manifestoSoftware engineering in the agile manifesto
Software engineering in the agile manifesto
 
Agile Development with Scrum.pptx
Agile Development with Scrum.pptxAgile Development with Scrum.pptx
Agile Development with Scrum.pptx
 
Session 14 2 Introducing Scrum At
Session 14 2 Introducing Scrum AtSession 14 2 Introducing Scrum At
Session 14 2 Introducing Scrum At
 
The Role of a BA on a Scrum Team IIBA Presentation 2010
The Role of a BA on a Scrum Team IIBA Presentation 2010The Role of a BA on a Scrum Team IIBA Presentation 2010
The Role of a BA on a Scrum Team IIBA Presentation 2010
 
Managing Agile Software Development Projects
Managing Agile Software Development ProjectsManaging Agile Software Development Projects
Managing Agile Software Development Projects
 
Introduction to Software Engineering
Introduction to Software EngineeringIntroduction to Software Engineering
Introduction to Software Engineering
 
Outsourcing With Agile
Outsourcing With AgileOutsourcing With Agile
Outsourcing With Agile
 
Agile Overview As V1.2
Agile Overview As V1.2Agile Overview As V1.2
Agile Overview As V1.2
 
Business Analyst As Product Owner
Business Analyst As Product OwnerBusiness Analyst As Product Owner
Business Analyst As Product Owner
 
Software Craftsmanship
Software CraftsmanshipSoftware Craftsmanship
Software Craftsmanship
 
Agile testing
Agile testingAgile testing
Agile testing
 

Postcards From The Agile Frontier Final

  • 1.
  • 2.
  • 3.
  • 4.
  • 5.
  • 6.
  • 7.
  • 8.
  • 9.
  • 10.
  • 11.
  • 12.
  • 13.
  • 14.
  • 15.
  • 16.
  • 17.
  • 18.
  • 19.
  • 20.
  • 21.
  • 22.
  • 23.
  • 24.
  • 25.

Notas del editor

  1. Note about title: shows I’m a BA: a really agile person would have entitled this “tweets frm the frntr”
  2. Colors here are hard to read—for “Visibility, Adaptability, and Business Value,” the top line represents agile development. For “Risk,” the top line represents traditional development and the bottom line represents agile development.
  3. Product Owner: says what should be done and whyScrum Master: makes sure agile processes are followedTeam: does everything else
  4. Oh oh. (Comes from Dean Leffingwell’s site)
  5. Anecdote: Bally Scrum Master Training
  6. The Goal Eliot Goldratt – read it! Simon Sinek “Start with the Why”