AT Pune 2014-Rahul shah significanceofproductownerforcd
•
0 likes•345 views
agile
Recommended
Recommended
More Related Content
What's hot
What's hot (11)
Viewers also liked
Viewers also liked (20)
Similar to AT Pune 2014-Rahul shah significanceofproductownerforcd
Similar to AT Pune 2014-Rahul shah significanceofproductownerforcd (20)
More from India Scrum Enthusiasts Community
More from India Scrum Enthusiasts Community (20)
Recently uploaded
Recently uploaded (20)
AT Pune 2014-Rahul shah significanceofproductownerforcd
- 1. Copyright © 2012 Allscripts Healthcare Solutions, Inc. Significance of Product Owner for Continuous delivery of valuable software Rahul Shah PMP, CSM, CSPO Project Manager Allscripts India Pvt. Ltd. 15th November 2014
- 2. | Copyright © 2012 Allscripts Healthcare Solutions, Inc. A Connected Community of Health Relay Team Race
- 3. | Copyright © 2012 Allscripts Healthcare Solutions, Inc. A Connected Community of Health ROE – Return on Energy
- 4. | Copyright © 2012 Allscripts Healthcare Solutions, Inc. A Connected Community of Health Vision = Motivation
- 5. | Copyright © 2012 Allscripts Healthcare Solutions, Inc. A Connected Community of Health Business Value
- 6. | Copyright © 2012 Allscripts Healthcare Solutions, Inc. A Connected Community of Health Continuous flow
- 7. | Copyright © 2012 Allscripts Healthcare Solutions, Inc. A Connected Community of Health Demo
- 8. | Copyright © 2012 Allscripts Healthcare Solutions, Inc. A Connected Community of Health What worked well @Allscripts
- 9. | Copyright © 2012 Allscripts Healthcare Solutions, Inc. A Connected Community of Health Questions – Do the homework
- 10. | Copyright © 2012 Allscripts Healthcare Solutions, Inc. A Connected Community of Health Communication
- 11. | Copyright © 2012 Allscripts Healthcare Solutions, Inc. A Connected Community of Health Pen it down
- 12. | Copyright © 2012 Allscripts Healthcare Solutions, Inc. A Connected Community of Health Feedback
- 13. | Copyright © 2012 Allscripts Healthcare Solutions, Inc. A Connected Community of Health Validate your assumption
- 14. | Copyright © 2012 Allscripts Healthcare Solutions, Inc. A Connected Community of Health What didn’t work @Allscripts
- 15. | Copyright © 2012 Allscripts Healthcare Solutions, Inc. A Connected Community of Health Keep Waiting
- 16. | Copyright © 2012 Allscripts Healthcare Solutions, Inc. A Connected Community of Health Bottle-neck
- 17. | Copyright © 2012 Allscripts Healthcare Solutions, Inc. A Connected Community of Health Email Chain
- 18. | Copyright © 2012 Allscripts Healthcare Solutions, Inc. A Connected Community of Health Customer specific requirement
- 19. | Copyright © 2012 Allscripts Healthcare Solutions, Inc. A Connected Community of Health One man show!
- 20. | Copyright © 2012 Allscripts Healthcare Solutions, Inc. A Connected Community of Health Thank You Email- Rahul.shah@Allscripts.com Linkedin- https://www.linkedin.com/in/rahultvp
Editor's Notes
- Product Owner is part of team.
- Return on energy
- Communicate Vision
- Business value
- Continuous, flow Let the requirements refine over time. Responding to external change and incorporating it. Principle 2: Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
- demo
- Ask questions. Multiple questions
- Setup a quick meeting to discuss/clear doubts Increase face-to-face time with PO Utilize every minute available.
- Prepare document and send it for confirmation. Email also will work. Penning down always helps and it opens door for detailed discussions. Abstracting doesn’t work anymore. Do your homework before the meeting.
- Feedback mechanism. Do multiple demos and ask for feedback.
- Validate your assumption, “maximizing amount of work not done” is important.
- Keep waiting
- Barrier – bottle neck One person – too many teams to handle
- Email chain
- Customer specific requirement doesn’t work
- Do not rely heavily on PO