Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
There are no answers, only stories.~ Garrison Keillor  MANAGEMENT:PRODUCT V. PROJECT                     by Karen Favazza ...
THE GENESIS OF AGILEBy Developers & for DevelopersImprove communication amongst themselvesImprove communication with the B...
WHAT THE BIZ HEARDDo it this way and you’ll get Better ProductsDo it this way and you’ll get More FasterDo it this way and...
THAT’S NOT WHAT WE SAIDThe simplicity of the Agile Development conceptmasks the complexity of Product Decision Making
AGILE PLANNING                   Level           Frequency             OwnerVision               1- Vision           6 - 1...
THE PRODUCT OWNER  The Man or Woman with Two Countries  ... with two jobs  ... with two constituencies  ... with two respo...
PRODUCT LINEA different type of “development”Strategy & TacticsROIIndustry Trends
MISUNDERSTANDINGS                   Life CycleProduct Management ≠ Project ManagementProduct Management ≠ Software Managem...
STRATEGY & TACTICSProduct Management requires                                   “...no matter how agile  Brainstorming    ...
KNOW YOUR CUSTOMERSPersonas - If it’s about the customer.1. Round 1: 24-36 1:1 Interviews based on   demographics of targe...
UNDERSTAND PRODUCT UXPersonas - If it’s about the Product Design.  Surveys  Web Analytics  User Experience  Contextual Int...
BOUNDARIES V. SILOSDevelopers need to understand Biz Case, Personas,etc.Product Management needs to actively participate i...
THE AGILE BACommunication in a Collaborative EnvironmentNot Part of the Agile TeamPart of the Customer TeamCollaborates, a...
THE BUSINESS ANALYSTCommunication in a Collaborative EnvironmentModeling: Capturing the complex conversationsaround Accept...
TWO TEAMS         - DEFINITION OF TERMS                                                Scrum Master                 Agile ...
STAKEHOLDERS                                 Characteristics           Agile BA               Cross Functional            ...
STAKEHOLDERS           Agile BA                 Responsibilities                                 ROI                      ...
PARADIGMSSome of this is just textbook Agile  Deciding the right thing to build and the RTM  strategy doesnt belong on the...
PARADIGMS & ECOSYSTEMSAgile is more than a bag of tips & tricks  Systemic approaches fail if parts of the system are  igno...
SYSTEMS DIAGRAMSystems Thinking: Senege, Peter. Fifth Discipline. 1990.Every group has its own story & its own ecosystem. ...
NAMES ARE POWERFUL WORDS         Conclusion:          Agile Technical Team         + Agile Product Team           Agile Pr...
Upcoming SlideShare
Loading in …5
×

Agile Prod Mgmt v. Proj Mgmt

2,536 views

Published on

Articulation of customer role & responsibilities in determining the right thing to build sets the Agile Technical Team up for success.

  • Be the first to comment

  • Be the first to like this

Agile Prod Mgmt v. Proj Mgmt

  1. 1. There are no answers, only stories.~ Garrison Keillor MANAGEMENT:PRODUCT V. PROJECT by Karen Favazza Spencer for Agile Coaches May 24, 2011 Pecha Kucha (20x20)
  2. 2. THE GENESIS OF AGILEBy Developers & for DevelopersImprove communication amongst themselvesImprove communication with the BizEliminate the “noise.”
  3. 3. WHAT THE BIZ HEARDDo it this way and you’ll get Better ProductsDo it this way and you’ll get More FasterDo it this way and we’ll be responsible for theproductDo it this way and we don’t need to bother withrequirement elicitation & documentationDo it this way and you don’t have to do all sorts ofthe other Product Management work. It’s MAGIC!
  4. 4. THAT’S NOT WHAT WE SAIDThe simplicity of the Agile Development conceptmasks the complexity of Product Decision Making
  5. 5. AGILE PLANNING Level Frequency OwnerVision 1- Vision 6 - 12 mo. BizRoadmapRelease 2- Roadmap 6 - 12 mo. Biz Sprint 3- Release quarterly Biz & Team Daily Scrum 4- Sprint 2 - 4 Wks Team 5- Scrum Daily Team based on Rally Chalktalk by Rachel Weston
  6. 6. THE PRODUCT OWNER The Man or Woman with Two Countries ... with two jobs ... with two constituencies ... with two responsibilities... SME... PRoduct Mgr... Customer Support....
  7. 7. PRODUCT LINEA different type of “development”Strategy & TacticsROIIndustry Trends
  8. 8. MISUNDERSTANDINGS Life CycleProduct Management ≠ Project ManagementProduct Management ≠ Software ManagementProduct Management should come first! Content is King!
  9. 9. STRATEGY & TACTICSProduct Management requires “...no matter how agile Brainstorming Development is, you’ll never build a successful product if the Financial Analysis work being done isn’t aligned to the company strategy and market needs.” Focus Groups Pragmatic Marketing Business Plan Market Analysis
  10. 10. KNOW YOUR CUSTOMERSPersonas - If it’s about the customer.1. Round 1: 24-36 1:1 Interviews based on demographics of target, and subsequent analysis2. Round 2: 5-7 Targeted Interviews per Persona3. Socialization & Usage: Introduce the Personas4. Keep in touch and update the Personas.
  11. 11. UNDERSTAND PRODUCT UXPersonas - If it’s about the Product Design. Surveys Web Analytics User Experience Contextual Interview Pricing & Placement
  12. 12. BOUNDARIES V. SILOSDevelopers need to understand Biz Case, Personas,etc.Product Management needs to actively participate inDevelopment/Testing. Collaboration Communication Boundaries
  13. 13. THE AGILE BACommunication in a Collaborative EnvironmentNot Part of the Agile TeamPart of the Customer TeamCollaborates, as necessary,assisting the PO, when POdoes not have the skillsAcceptance Test Driven DesignCartoon used with expressed permission ofModernAnalyst.com, the premier online communityfor business analysts.
  14. 14. THE BUSINESS ANALYSTCommunication in a Collaborative EnvironmentModeling: Capturing the complex conversationsaround Acceptance Criteria.Simulations: User Experience analysis usingprototypes prior to full development to determine ifthe vision is the right thing. Identifying the Right Thing Before bringing it to the Technical Agile Team!!
  15. 15. TWO TEAMS - DEFINITION OF TERMS Scrum Master Agile BA Product OwnerCustomer Team Agile Team (technical) aka 3 Roles Stakeholders Cross FunctionalSteering Committee The BusinessProduct Management
  16. 16. STAKEHOLDERS Characteristics Agile BA Cross Functional Big View SME detail Collaborative LEAN approach Product OwnerCustomer Team The What & The Why
  17. 17. STAKEHOLDERS Agile BA Responsibilities ROI Market Research Industry Changes Project Charter Persona Development Product Owner Collaborating with the PO Authoring User Stories Providing Feedback to Tech Team Backlog Grooming UATCustomer Team The What & The Why
  18. 18. PARADIGMSSome of this is just textbook Agile Deciding the right thing to build and the RTM strategy doesnt belong on the Agile Teams plate. All the Agile Team should do is build what theyre told to build, how they decide is best.
  19. 19. PARADIGMS & ECOSYSTEMSAgile is more than a bag of tips & tricks Systemic approaches fail if parts of the system are ignored. Child’s Song Fishbone Problem Analysis
  20. 20. SYSTEMS DIAGRAMSystems Thinking: Senege, Peter. Fifth Discipline. 1990.Every group has its own story & its own ecosystem. Execs Marketing Product Agile Team Rivals Backlog Envir Mgmt Process Industry
  21. 21. NAMES ARE POWERFUL WORDS Conclusion: Agile Technical Team + Agile Product Team Agile Project Team Scale agility within the organization by calling out theProduct Team by name and by articulating their unique role & multiple responsibilities.

×