Agile india2012 po role_can you hear me now

Download Agile india2012  po role_can you hear me now

Post on 13-Dec-2014

214 views

Category:

Technology

1 download

Embed Size (px)

DESCRIPTION

presented at agile 2011 & agil

TRANSCRIPT

<ul><li> 1. PO RoleCAN YOU HEAR ME NOW? Belkis Vasquez McCall </li> <li> 2. Belkis Persona Senior Product Owner Important to Know about Belkis: Has over 14 years of IT experience Spent past 6+ years leading and coaching project teams Collaborated with other Agile experts on defining the Product Owner role Belkis philosophy: 1. Successful people do what unsuccessful people dont dare. 1 </li> <li> 3. As a PO, I use personasPersonas highlighted in this presentation Director of Applica- Former Project Managers tion developmentFormer Business Analysts Important to know about us Are part of a globally distributed application development group Have over 5 years of Agile experience Deliver high business value IT systems 2 </li> <li> 4. As a PO, I use personasBuilding quality products starts with you 3 </li> <li> 5. As a PO, I use simple vision documentVision and goals for today VisionHighlight how the PO role has helped former Business Analysts and Project Managersexercise their influence beyond project execution into product experience Goal: Getting our voices heard at the product level! 1 Share best practices from PMs and BAs that have transitioned to the PO role 2 Highlight how the PO role has impacted the success of our organization 3 Explore together how as PO we can amplify our voices at the program and organizational level 4 </li> <li> 6. 1 Challenges we faced as Business AnalystsAs a BA, I struggledwriting big documentsthat team members didnot understand 5 </li> <li> 7. 1 Challenges we faced as Business Analysts As a BA, I struggled with spending a lot of time being a requirement master to ensure developers understood the product 6Source: http://urbantitan.com/wp-content/uploads/2011/02/crazy-school-teacher-300x270.jpg </li> <li> 8. 1 Challenges we faced as Business AnalystsAs a BA, I struggledwith the concept ofownership and gettingthe team to be alignedwith the product vision 7 </li> <li> 9. 1 Challenges we faced as Project Managers Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct NovAs a PM, I struggled Inception Phasewith scope creep andstill meeting thecustomer deadline Elaboration Phase It 1 It 2 It 3 Construction Phase It 1 It 2 It 3 It 4 Transition Phase (Weekly Its) Release Window 8 </li> <li> 10. 1 Challenges we faced as Project ManagersAs a PM, I struggledwith expectationsetting and gettingeveryone to understandtheir role 9 </li> <li> 11. 1 Challenges we faced as Project ManagersAs a PM, I struggledwith lack of trans-parency and notknowing the progressof the team 10 </li> <li> 12. As a PO, I use value the agile principlesUsed the four Agile principles to overcome our challenges 1. Individuals and 2. Working software over interactions over comprehensive processes documentation and tools 3. Responding to change 4. Customer over following a plan collaboration over contract negotiationSOURCE: www.agilemanifesto.org (March 2008) 11 </li> <li> 13. 1 PO practices from former BAs and PMs that helped them As a PO, I use develop better products 12 </li> <li> 14. 1 Best practices from Business Analysts that have transitioned As a PO, I use to the PO roleAs a PO, I writesimple, Just in timedocuments that teammembers can easilyunderstand 13 </li> <li> 15. 1 Best practices from Business Analysts that have transitioned As a PO, I use to the PO roleAs a PO, I encouragethe team to be part ofdesign andrequirementsdiscussions to ensurecollective ownership ofthe product 14 </li> <li> 16. 1 Best practices from Business Analysts that have transitioned As a PO, I use to the PO roleAs a PO, I sign-offrequirements andfeatures to help movethe release forward 15 </li> <li> 17. 1 Best practices from Project Managers that have transitioned to the PO roleAs a PO, I use scopeburn down to trackscope creep and helpthe sponsors maketrade-offs 16 </li> <li> 18. 1 Best practices from Project Managers that have transitioned to the PO roleAs a PO, I use thesprint burn up chartto understand ourprogress and indentifyrisks 17 </li> <li> 19. 1 Best practices from Project Managers that have transitioned to the PO roleAs a PO, I leveragesprint artifacts to geteveryone to understandtheir role 18 </li> <li> 20. As the director of2 IT leadership explains how the PO role has impacted Application Development my perspective on the PO the success of our organization role is 19 </li> <li> 21. 2 Our practices have evolved with the PO role Becoming Decision Adapting light MakerTranslating weight practicesrequirements BUILDING BETTER PRODUCTS! 20 </li> <li> 22. As a PO, Im adapting to3 Start exploring how POs can amplify their voices changes in the role at the program and organization level Product Owner involvement in the product experienceProduct Genesis Product Creation Product Evolution User research Present Future Usage analytics Work on activities Work on Rapid Prototyping from current preparing/ User research Personas sprint prioritizing User behaviors stories for 2-3 Story boarding 2 sprints ahead Enhancements 3 High-level Backlog Sprint Evolving needs of the market cycle activities 1 Planning produc- 4 tion Past releases Close-out open stories from previous sprints DECISION TO MOVE FORWARD VALUABLE FUNCTIONALITY NEXT 2-3 FUTURE RELEASES WITH SOLUTION AVAILABLE TO USERS 21 </li> <li> 23. Key ingredients for being a Product Owner that is heard and successful Creates collective ownership of the product vision and roadmap PO Role Can You Hear Me Now? Works with stakeholders and team to manage scope and priorities Empowered to make decisions and helps the team adapt to evolving user needs 22 </li> <li> 24. Lessons learned with transitioning to the PO role Getting stakeholders and team members used to just in time requirements takes time Taking on a leadership role for a release is rewarding but can also be overwhelming at first The constraints with time, forces you to make decisions now and not put them off for later 23 </li> <li> 25. Group exercise 24 </li> </ul>