Way to Agile - USTH
•
1 like•963 views
My presentation in Agile4U (Agile for University) program of HanoiScrum in 2013. This presentation may have some customised content for University of Science and Technology of Ha Noi.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Way to Agile - USTH
Similar to Way to Agile - USTH (20)
More from Hien Nguyen
More from Hien Nguyen (12)
Recently uploaded
Recently uploaded (20)
Way to Agile - USTH
- 1. AgileAgile way to Nguyễn Văn Hiển 2013
- 2. Way to Agile Nguyễn Văn Hiển hien@hanoiscrum.net Agile4U
- 3. Content Software Development MethodologiesAgile and Agile processes XP Scrum Lean & Lean Startup Agile NOW! Mindset Techniques Collaboration Tools
- 4. How is a software created?
- 5. Someone wants a software to meet his needs investigates and assigns some people to create one with required features, that’s called REQUIREMENTS
- 6. And, some of these people draw something, that’s called DESIGN
- 7. Then others type the statements, follow the design , that’s called CODING
- 8. After that, other execute the software to make sure it meets the requirements, that’s called TESTING
- 9. Hopefully, a SOFTWARE will be released with full related documents, CONTRACT will be paid, CUSTOMER will be over-‐satisfied Wonderful ending…
- 10. But, wait. The fact is… Source: The CHAOS Manifesto, The Standish Group, 2012. 14% 57% 29% Thành công Thử thách Thất bại Successful Challenged Failed
- 11. Customers are so disappointed… What customers need What we promise What customers pay What customers receive Images: http://natishalom.typepad.com/nati_shaloms_blog/2008/04/one-‐requirment.html
- 12. Why?
- 13. !
- 15. HOW DOES SCRUM TEAM CREATE A SOFTWARE ??
- 16. Someone wants a software to meet his needs, investigates and assigns some people to create one with requiredfeatures, that’s called REQUIREMENTS
- 17. Software creation work is assigned to Development team This team work together and do Planning What will be done in next month/week to have (some) completedfeature(s) to releaseat end of next month/week
- 18. Result of planning meeting is a Plan that includes goals followed by work that needs to completed in this month/week
- 19. Work is disseminated to each team member. Members will work with close collaboration The team has daily meeting L 15 minutes/day to update, check the working progress, and fix rising issues.
- 20. Just-‐in-‐time update plan if necessary
- 21. Iterate working till end of time box
- 23. RELEASABLE software What will we have?
- 24. Not done yet, development team should have a reflection meeting HOW did team WORK? Could team work BETTER? Try to find out some points that should be IMPROVED in next month/week
- 26. Scrum Framework
- 27. Differences?
- 28. Scrum concentrates on: Collaboration over document Customer problem solving over contract signing Scrum quickly respond to changes! Customers can receive software right after one month, or one week
- 29. Agile umbrella! Scrum XP Lean Software Development Crystal DSDM Agile FDDAgile UP
- 30. eXtreme Programming Read more: http://www.hanoiscrum.net/hnscrum/learning/167 Principles • Rapid Feedback • Assume Simplicity • Incremental Change • Embracing Change • Quality WorkValue • Communication • Simplicity • Feedback • Respect • Courage Develop software with highest quality, lowest cost, fewest bugs, hyper productivity and maximize ROI
- 33. Lean Software Development Apply Lean thinking in software development 7 WASTES 1. Extra Features 2. Handovers 3. Task Switching 4. Work in Progress 5. Failure Demand 6. Delays 7. Defects Read more: http://www.hanoiscrum.net/hnscrum/learning/168-‐agilemethod3-‐lean-‐software-‐development 7 principles 1. Eliminate Waste 2. Create Knowledge 3. Defer Commitment 4. Deliver Fast 5. Respect People 6. Build Quality In 7. Optimize The Whole
- 35. Generalization | Unique Image: Hendrik Kniberg
- 36. BEHIND THE SCENES ...
- 37. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others to 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. Source: AgileManifesto.org
- 38. Just-‐in-‐time Daily update Daily Standup Plan, responding to change
- 41. Why Agile?
- 42. Agile now!
- 43. Agile now Each team has 2 people: -‐ 1 controls with commands: GO, STOP, TURN LEFT, TURN RIGHT -‐ 1 follows another’s commands è Goal: In 30 seconds, make highest number of “high quality steps”.
- 44. Why Agile? As in US law 100% projects of Ministry of Defence must use Agile! 42% 49% 9% Successful projects Thành công Thử thách Thất bạiSuccessful Challenged Failed
- 45. Why Agile? -‐ Significant experience in usage of modern PHP frameworks (Yii, Zend ...) -‐ Professional knowledge of JavaScript / Jquery/Ajax, CSS, XML, HTML, CMS. -‐ Magento, Drupal, Zoomla experience is preferred. -‐ Experience of web development. UI and usability understanding. -‐ HTML5 is a plus -‐ SEO experience is preferred Source: http://www.vietnamworks.com/senior-‐php-‐software-‐engineer-‐based-‐hcmc-‐401465-‐jv Source: http://www.vietnamworks.com/php-‐developers-‐with-‐good-‐front-‐end-‐skills-‐html-‐css-‐js-‐400081-‐jv -‐ Read and understand requirement specification -‐ Create Detail Design independently -‐ Create System Design with instruction from Team Leader/ Senior Team Leader -‐ Do coding and unit test -‐ Do reviewing source code & design documents
- 46. Lean Startup Assumption, experimental Feedback data Problems? Solutions?
- 48. Minimum Viable Product Product has minimum feature, fast release • No extra features • Optimize from feedback data Build
- 49. Read more 49
- 50. Resources • HanoiScrum.net • AgileAtlas.org • ScrumAlliance.org • AgileAlliance.org • Các hội thảo Agile Tour, ScrumDay… • Tool Vendors (MSDN, IBM, VersionOne…)
- 52. Thank you!