Meetup #4 Agile Mindset
0 likes107 views
The document discusses the Agile mindset and summarizes the Agile manifesto principles established in 2001 by software experts who sought more effective development methods. It details the structure and characteristics of Scrum teams, emphasizing self-organization and shared accountability, along with the importance of a clear 'Definition of Done' for product increments. Additionally, it highlights the need to reduce work in progress to improve functional outcomes, advocating for a focus on completing user stories.
Meetup #4 Agile Mindset
- 1. Agile Mindset Diana Yulinda & Dinar Trifiana
- 2. Introduction
- 3. Agile
- 4. Agile Agile?
- 5. History Of Agile Manifesto In 2001, group of software experts (John Kern, Kent Beck & etc) met at The Lodge at Snowbird ski resort in Utah • Frustration & felt not productive with the method used ( time lag ) • Customer mindset the process will be the same in every development
- 6. Individuals & Interactions Processes & Tools over Working Software Comprehensive Documentation over Customer Collaboration Contract Negotiation over Responding to Change Following a Plan over We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Agile Manifesto
- 7. Example of User Story As a <user role> I want <goal> so that <benefit> As a student I want to purchase a parking pass so that I can drive to school.
- 8. Agile is not create good product, good culture does Agile
- 10. Human is not resource
- 11. Scrum Team
- 12. Development Team The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of "Done" product at the end of each Sprint Scrum Team
- 13. Development Team Development Teams have the following characteristics : • Self-organizing • Cross functional • Scrum recognizes no titles for Development Team members • Scrum recognizes no sub-teams in the Development Team • Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole Scrum Team
- 15. Definition of Done When a Product Backlog item or an Increment is described as "Done", everyone must understand what "Done" means
- 16. All automated test script has been created Unit test Integration test Functional test Performance test Security test Coded UI test Mission critical business methods Pair programming Code reviewed by the whole team Covered by automated tests and covered should not be lower than 85% Documentation has been created with best effort User requirement specification User guide and user manual Architecture & Technical specification Page loading should not than 2 seconds Sexy and clean UI/UX PO can deploy with a single click with button Release We are proud to mention this software in our resume DoD Example Definition of Done
- 17. Definition of Done Source: Manajemen Modern dengan Scrum, Joshua Partogi Increment must be “DONE”, there’s no “almost done ”. To have a clear understanding of the meaning of DONE, Development Team should create a Definition of Done When a Product Backlog item or an Increment is described as "Done", everyone must understand what "Done" means “Done” or “Not Done” Avoid the 90% syndrome
- 19. Agile Thinking : Stop Starting Start Finishing By having too many work in process items, it looks like everybody is busy but there is no functional outcome for the end user. So, instead, it’s important to work towards completing the user-story.
- 20. Agile Thinking : Stop Starting Start Finishing
- 21. Paper Plan Game - 1 Rules: • Build Paper Airplanes • Timebox 2 minutes • Each time have 3 specialist • Each Airplanes must be unique • Airplanes must flying and reach the Facilitator
- 22. Paper Plan Game - 2 Rules: • Build Paper Airplanes • Timebox 2 minutes • No Specific rules • Each Airplanes must be unique • Airplanes must flying and reach the Facilitator
- 23. SCRUM ON!