Agile Methodologies in Project Management

Presentation about agile methodologies, their principles, motivations and impacts in real world. Concepts and principles of Extreme Programming, Lean, Kanban and Scrum are outlined here.

Transcript

1. Agile Methodologies in Project Management Victor Corrêa victorac@gmail.com
2. Traditional Models
3. Waterfall Model Requirements Analysis System Design Implementation Tests and Integration Operation and Maintenance
4. Formal Specification Model
5. Evolutionary Model Prototyping Quick Feedback
6. Evolutionary Model Incremental Iterative
7. Agile Methodologies
8. Agile Manifesto Individuals and interactions Processes and tools Working software Comprehensive documentation
9. Agile Manifesto Customer collaboration Contract negotiation Respond to change Follow a plan
10. 12 Agile Principles • Satisfy the client through early and continuous delivery of software with aggregated value • Change in requirements are always welcome, even if late • Frequently deliver working software, from a few weeks to a few months, preferring shorter intervals • Business and development people should work together • Build software around motivated individuals and trust them to do their job • The best way to transmit information to and across the development team is face to face communication
11. 12 Agile Principles • Working software is the primary measure of progress • Sustainable development yields a constant and indefinite pace • Continuous attention to technical excellence and good design increases agility • Simplicity – the art of maximizing the amount of work not done – is essential • Teams are self-organized • Regularly the team meets to evaluate improvements, decides how to become more efficient and refine its behavior
12. Cost of Change
13. Cost of Change
15. Workflow – Waterfall Model Requirements Documentation Analysis Design Implementation Tests Production Requirement #1 Requirement #2 Requirement #3
16. Workflow – Agile Model Analysis Design Implementation Tests Production Requirement #1 Requirement #2 Requirement #3
17. Extreme Programming
18. XP Concepts • Release and Iteration Planning • User Stories • Acceptance and Unit Tests • Investigations (Spikes) • Iterations • Stand Up Meetings
19. XP Concepts • Pair Programming • Test Driven Development • Continuous Integration • Client inside the team • Team Velocity
26. Lean
27. Lean Principles • Eliminate waste • Unnecessary code or feature • Commit to more than what is feasible to complete • Delay in the software development process • Unclear or dynamic requirements • Bureaucracy • Slow or not effective communication • Work partially done • Defects and quality issues • Task switching
28. Lean Principles • Build quality in • Tests specify the behavior and document the code • Tests give security to perform modifications • Integrate components early and frequently • Do not tolerate defects, fix them as quickly as possible • Create knowledge • Knowledge brief • Wiki • Code reviews • Documentation • Diagrams
29. Lean Principles • Delay commitment • “The Last Responsible Moment” • Account for flexibility in the design • Deliver quickly • Focus on the workflow efficiency, not resources efficiency • Avoid the “this is not my job” • Simplicity is key • “How long does it take to release to the market 1 extra line of code?”
30. Lean Principles • Respect people • Give them purpose and challenges • Support the team • Optimize the whole • Know what the purpose of your product is • Avoid making decisions that optimize specific modules • Think in the long term
31. Kanban
32. Kanban
33. Kanban Principles • Visualize the work • Limit the work in progress • Focus on the flow • Continuous improvement
34. Scrum
35. Pilars of Scrum • Transparency • Inspection • Adaptation
37. When to use? KANBAN BOKs
38. In practice...
39. Summarizing...
41. Adaptability Previsibility
43. Thank you! Victor Corrêa victorac.public@gmail.com