Product Owner Briefly

5,209 views
4,981 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
5,209
On SlideShare
0
From Embeds
0
Number of Embeds
955
Actions
Shares
0
Downloads
171
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
  • Iteratívny a inkrementálny vývoj zvyšuje viditeľnosť
  • Art of maximizing the amount of work not done is essential.
  • Product Owner Briefly

    1. 1. 1<br />Product owner<br />…introduction of the most challenging role<br />
    2. 2. Dusan Kocurek<br />http://twitter.com/didierkoc<br />
    3. 3. Goal<br />We are going to open a talkabout<br />Agile <br />&<br />Product Ownership<br />3<br />
    4. 4. What are your current concerns <br />about the way how products are developed <br />and what is delivered?<br />4<br />
    5. 5. Concerns I heard often<br />5<br />
    6. 6. How many <br />features are/are not<br />used in products <br />you manage/use?<br />6<br />
    7. 7. Real life of features<br />Scott Ambler, IBM<br />
    8. 8. Real life of features<br />WHY?<br />Scott Ambler, IBM<br />
    9. 9. Customers<br />Changes<br />Competition<br />9<br />
    10. 10. Waterfall challenges<br />
    11. 11. Waterfall challenges<br />HOW?<br />
    12. 12. Typical way to solve issues<br />12<br />
    13. 13. Agile is one possible alternative….<br />What Agility<br />in software development<br />means?<br />13<br />
    14. 14. Agility is the ability <br />to both create and respond to a change<br />in order to profit <br />in turbulent business environment<br />Jim Highsmith, 2002<br />14<br />
    15. 15. Agile Manifesto<br />
    16. 16. Change factor<br />Involve customer<br />in close collaboration<br />with development team<br />16<br />
    17. 17. Simple principle<br />CCC<br />Cards<br />Confirmation<br />Conversation<br />
    18. 18. 18<br />Feedback<br />Less communication channels<br />Pride & shame moments<br />Understanding of your potentialities<br />Planning according current needs<br />Doing what is necessary as late as possible<br />Additional sell channel <br />It hurts<br />It take time<br />Meetings<br />Changes to be happened<br />Conflict with Date drive development<br />Contracts<br />Organization change<br />Involved customer<br />Positive<br />Negative (?)<br />
    19. 19. Coins<br />Game!<br />Stopwatch<br />
    20. 20. versus<br />
    21. 21. Waterfall vs. Agile<br />
    22. 22. Agile approach<br />This is not possible…..<br />We are different…..<br />We can’t…..<br />
    23. 23. If you would like to construct <br />the building, <br />will you check how it looks<br />once is it built?<br />23<br />
    24. 24. Check & deliver<br />24<br />A value in Agile is delivered during the development, not just at the end <br />Waterfall<br />Agile<br />
    25. 25. How to develop in a different way<br />Incrementalor iterative?<br />
    26. 26. Simplified Agile productlife cycle<br />
    27. 27. Simplified Agile productlife cycle<br />Benefits?<br />Disadvantages?<br />
    28. 28. Component vs. feature orientation<br />Component orientation<br />Feature orientation<br />
    29. 29. Is agile product different?<br />29<br />
    30. 30. Scrum overview<br />30<br />
    31. 31. Roles<br />
    32. 32. Shock Therapy…<br />
    33. 33. Product Owner<br />Father of the product<br />Vision<br />Features<br />Priority<br />Planning<br />
    34. 34. Key Product Owner Attributes<br /><ul><li>A subject matter expert
    35. 35. Knowledgeable about the business
    36. 36. Facilitates stakeholder input
    37. 37. Has decision making authority
    38. 38. Uses the system being developed
    39. 39. Understands the key role of a Product Owner in Scrum
    40. 40. Has lots of time for the team, good communicator
    41. 41. Helps the team to improve</li></ul>© Innovel LLC<br />
    42. 42. Story<br />35<br />Why?<br />Who is writing it?<br />Who is using it?<br />How detailed?<br /> As a <user><br /> I can <do something><br /> so that <user value received><br />Acceptance Criteria<br />Business Value<br />Priority<br />
    43. 43. Agile Requirements<br />
    44. 44. Scrum<br />
    45. 45. Different levels of granularity<br />Product planning<br />
    46. 46. Parallel worlds<br />
    47. 47. Planning<br />
    48. 48. 41<br />
    49. 49. …what’s left<br />42<br />
    50. 50. Iteration (sprint) tracking<br />
    51. 51. Product BurnDown chart<br />44<br />
    52. 52. …summary<br />45<br />
    53. 53. Product Owner should expects<br />46<br />
    54. 54. Product Owner Responsibilities<br />47<br />
    55. 55. What is different in Agile<br />Customers on board<br />Less documentation<br />More collaboration<br />Improve product continuously daily<br />More meetings, but more productive<br />Near time planning preferred<br />Details are added as late as possible<br />Smaller development groups<br />48<br />
    56. 56. …thank you<br />49<br />Is your customer the driver?<br />
    57. 57. Add I. - Product Who?<br />50<br />

    ×