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.

[DevDay2019] Agile & Scrum - Power of Mastering the Basics - By Son Tang, Director of Delivery at KMS Technology Vietnam

87 views

Published on

Agile and Scrum is not a new concept. Nowadays, many team has been using Scrum and adopting Agile. But do they really using those right way to get all benefit from Agile and Scrum?
Understanding Agile & Scrum benefit not only Manager or Team lead but also team members, so they can really be a part of Agile/Scrum team. This topic will provide knowledge in Agile/Scrum as well as explain deeply them with real-life examples.

Published in: Technology
  • Be the first to comment

[DevDay2019] Agile & Scrum - Power of Mastering the Basics - By Son Tang, Director of Delivery at KMS Technology Vietnam

  1. 1. Agile and Scrum training DEVDAY 2019 April 06, 2019
  2. 2. Agenda 1 Agile mindset 2 Scrum framework 3 Example 4 Q & A
  3. 3. Agile Mindset
  4. 4. Imaging we are trying to set a comfortable room’s temperature for everyone. But you can only set once and cannot adjust it until the end of the day. What can go wrong ?
  5. 5. There are a lot of things could impact to room’s temperature: o Number of people in room o Metabolism of each person o Activity of each person o Opening/closing of doors o Weather: including sun, clouds, and outside temperature o Temperature of adjoining rooms o Construction material of the building o Floor of the room o ….. You name it
  6. 6. But…. setting room’s temperature should be simple, right? How about building a software ?
  7. 7. You don’t know everything
  8. 8. History won’t help even if you build same thing again
  9. 9. Pirates know the best to deal with complex situations: “Check your ship, your compass and sail. The storm will come, we don’t know when but when it happens, we check the ship, the compass and sail”
  10. 10. Agile’s core value Individuals and Interactions Over Processes and Tool We don’t know everything and we need to react to situations that is why people will be key and communication will be the door. Working Software Over Comprehensive Documentation Things will changes and details documents will be wasted. Agile values working software more to eliminate the unnecessary wasted documents that cause the delay in development. Customer Collaboration Over Contract Negotiation Contract can keep we safe, an engaged customer can keep both happy Responding to Change Over Following a Plan We cannot have a perfect plan at the beginning. Changes always improve a project and provide additional value Agile is ability to rapidly and deliberately response to changes while controlling risk.
  11. 11. Being Agile doesn’t mean just do whatever we want Being Agile mean you are ready to lead
  12. 12. Scrum framework
  13. 13. Scrum is a framework
  14. 14. o Helps people effectively address complex problem o Productively and creatively deliver products of highest possible value
  15. 15. You cannot have more time, but you can do more valuable things
  16. 16. How to be transparency ?
  17. 17. Everyone need to agree when things is ”done”
  18. 18. Definition of Done is an agreement between development team and PO so they could know when thing is ”done”
  19. 19. We only have two status in Scrum: Done and Un-Done
  20. 20. Let learn Scrum in one slide
  21. 21. What is a Sprint in Scrum Sprints are time-boxed iterations that serve iterative-incremental development. All development is done with in a Sprint A Sprint contains the time-boxed Scrum events A Sprint is 1 month or less and it’s best to have a consistent duration Scrum knows no phases, only Sprints The entire point of Scrum is to create a Done Increment.
  22. 22. Sprint is an Agreement
  23. 23. Scrum doesn’t need a plan, but it needs planning
  24. 24. Sprint goal Sprint backlog Product backlog Techniques for estimation size Who assigns work for development team? Can development team modify Sprint backlog? Can development team change sprint scope? Sprint planning
  25. 25. 15 minutes time-box daily Consistent place and time Development team inspect their progress toward the Sprint goal Development team creates a plan for next 24h Not a status meeting Not a problem solving meeting Work remaining is updated daily What are 3 questions in daily meeting? What does the team do if some problem arise during daily meeting? Daily Scrum
  26. 26. What’s Sprint Review? Who can join Sprint review? Agenda Product demonstration PO declares what’s done Stakeholder feedback Video Sprint review Sprint Review
  27. 27. Scrum team inspects how the last sprint went People, relationship, process, tools DoD Scrum team select improvements for implementation next Sprint Sprint Retrospective
  28. 28. Inspect the Increment The Product Owner informs the team of the Velocity required for the next Sprint Figure out how to make the next Sprint more enjoyable The Scrum Team inspects itself Inspect Product Backlog and likely completion dates Adapting the definition of “Done” to increase product quality A demo to promote the product to the stakeholders Inspect how the Sprint went with regards to people and relationships Stakeholders applaud the Development Team for their hard work Inspect marketplace changes and potential use of the product Adapt the Product Backlog A status meeting for the steering committee Sprint Review Sprint Retrospective
  29. 29. Sprint Review Sprint Retrospective Inspect the Increment The Product Owner informs the team of the Velocity required for the next Sprint Figure out how to make the next Sprint more enjoyable The Scrum Team inspects itself Inspect Product Backlog and likely completion dates Adapting the definition of “Done” to increase product quality A demo to promote the product to the stakeholders Inspect how the Sprint went with regards to people and relationships Stakeholders applaud the Development Team for their hard work Inspect marketplace changes and potential use of the product Adapt the Product Backlog A status meeting for the steering committee
  30. 30. What is the most important value of your “dream” team ?
  31. 31. Event Inspection Adaption Who attends Time-box for 2weeks Sprint Planning Product backlog Sprint goal, Forecast, Sprint backlog Scrum team 4 hours Daily Scrum Progress toward Sprint goal Sprint backlog Development team 15 minutes Sprint Review Increment, Sprint, Product backlog Product backlog Scrum team Stakeholders 2 hours Sprint Retrospective Sprint Actionable and committed improvements Scrum team 1.5 hours o “Do, or do not. There is no try.” o Done and Undone o Technical debts: stop creating & pay back a small technical debt each Sprint Take Away
  32. 32. Example
  33. 33. Question & Answer
  34. 34. Appendix Agile’s values and principles

×