Successfully reported this slideshow.
Your SlideShare is downloading. ×

Starting the product for FIIT Bratislava

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Loading in …3
×

Check these out next

1 of 38 Ad

Starting the product for FIIT Bratislava

How to develop product ready for change using agile approaches? In this presentation you will find out how to combine different approaches in to one product development framework.

How to develop product ready for change using agile approaches? In this presentation you will find out how to combine different approaches in to one product development framework.

Advertisement
Advertisement

More Related Content

Advertisement

Similar to Starting the product for FIIT Bratislava (20)

More from ScrumDesk (20)

Advertisement

Recently uploaded (20)

Starting the product for FIIT Bratislava

  1. 1. Starting the product: You better take the right approach Efficient agile practices
  2. 2. Dušan Kocúrek Agile Coach Chief Product Owner potrebujemporadit@scrumdesk.com www.scrum.sk www.scrumdesk.com @scrumdesk
  3. 3. What to cook? For who? Why? What do they like? What do we have? What do I know? How much time?
  4. 4. TRADITIONAL ALAPASAP AGILE PUSH P1 P1 P2 PULL 1st 2nd 3rd
  5. 5. Agile practices Scrum XP TDD DevOps Continuous Integration ...........
  6. 6. HOW why Forwho
  7. 7. Theirs pain?
  8. 8. A journey of new product To know (5 days) To be (2 days) To prosper (2 days)To plan (3 days)To make 1 2 345
  9. 9. Know your customers Value Proposition Canvas
  10. 10. Personas Know your customers http://www.scrumdesk.com/Download/Documents/AgileResources/Persona.pdf
  11. 11. For customers who need something product name is product category which main benefit comparing to competition our product is different by Just one sentence
  12. 12. less > more Bardzo szybki i łatwy w obsłudze menadżer plików. W celu ułatwienia eksplorowania zasobów komputera aplikacja umożliwia otworzenie do 10 paneli nawigacyjnych.
  13. 13. Minimum Marketable Product Perfection can not be achieved when there is nothing to add, but nothing to remove.
  14. 14. Scrum 10
  15. 15. Lead your power •For who •Problem Let’s start •Elevator Statement •Lean Canvas A vision •Features, epics •User stories map Backlog • MoSCoW • Business value Prioritize • An order • An estimation • Sprit slotting Release Planning • Planning • Development • Review • Retrospective Sprint #1 • Planning • Development • Review • Retrospective Sprint #2 I. Does it make sense? II. Get ready III. Make up your dreams
  16. 16. Scrum extended. Just a little bit. Plánovanie release Sprint 1 Sprint 2 Sprint 3 Sprint 1 Sprint 2 Sprint 3 Plánovanie release Backlog Release
  17. 17. Agile requirements
  18. 18. What is he doing? Who What Why CONTEXT
  19. 19. A key to user 5 Why
  20. 20. Perfect user story Independent Negotiable Valuable Estimable Sizeable Testable 3-5 days Acceptance criteria Story points Subtasks Test in DoD
  21. 21. User story template
  22. 22. User Stories Map
  23. 23. Prepare a plan Before the planning Plan Onsite All team members Always physical cards
  24. 24. When will we be there?
  25. 25. Relatively is better
  26. 26. Planning poker Discussion Everybody has voice All team members One result An agreement 3 rounds 0 ½ 1 2 3 5 8 13 20 40 100 ?
  27. 27. Get the rhytm! Know your cards Acceptance inside
  28. 28. Add extreme Code Review = MUST Refactoring = A rule Product Owner = ACTIVE LISTENER
  29. 29. Are we there?
  30. 30. Don’t forget to improve
  31. 31. http://scrum.sk/index.php/zdroje/knihy-a-dokumenty/
  32. 32. AGILE a
  33. 33. Scrum Guidelines www.scrum.sk, Zdroje, Knihy a dokumentacia http://www.scrumdesk.com/Download/Documents/AgileResources/ScrumGuidelinesSK.pdf
  34. 34. {Q} – {A} = 0
  35. 35. www.scrum.sk potrebujemporadit@scrumdesk.com www.scrumdesk.com

×