Agile Project Management

Transcript

1. Agile Project Management Introductory Training
2. What is Agile? Agile project management is an iterative approach to managing software development projects that focuses on continuous releases and incorporating customer feedback with every iteration.
3. Why Implement Agile? Accelerated product delivery Enhance ability to manage changing priorities Increase productivity Improve software quality Enhance delivery predictability Improve business and IT alignment
4. Agile Manifesto
5. Agile Principles
6. 12 Agile Principles Customer Satisfaction Welcome changing requirements Frequent delivery of working product Daily collaboration Motivated individuals Face to Face Meetings Working product: Measure of Success Sustainable pace Continuous attention to Technical Excellence Simplicity Self-Organizing Teams Regular reflection for continuous improvement
7. Customer Satisfaction Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. customer satisfaction highest priority early delivery continuous delivery valuable software
8. Welcome Changing Requirements Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage. changing even late competitive advantage customers
9. Frequent Delivery Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Working software Frequently Shorter timescale
10. Daily Collaboration Business people and developers must work together daily throughout the project. must work together throughout
11. Motivated Individuals Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. build projects motivated individuals support in need trust done
12. Face to Face Meetings The most efficient and effective method of conveying information to and within a development team is the face- to-face conversation. efficient effective conveying face-to-face
13. Working Software Working software is the primary measure of progress. working primary measure progress
14. Constant Pace Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. sustainable development constant pace
15. Continuous Attention to Technical Excellence Continuous attention to technical excellence and good design enhances agility. continuous attention excellence good design agility
16. Simplicity Simplicity — the art of maximizing the amount of work not done — is essential. simplicity reducing waste removing impediments
17. Self-organizing Teams The best architectures, requirements, and designs emerge from self-organizing teams. self-organized fully-refined requirements
18. Regular reflection for Continuous Improvement At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. regular reflection sanity check behavioral adjustments
19. Agile Roles
20. Agile Roles Development Team Scrum Master Stakeholders Agile Mentor Product Owner
21. Product Owner “Customer Representative” Responsible for bridging customer, business stakeholders and development team Expert on product and customer needs and priorities Works with development team daily Shields development team from organizational noise Decisive to make tough business decisions
22. Development Team The people who create the product Designers Programmers Testers Data Engineers
23. Scrum Master “Project facilitator” Responsible for supporting development team Clearing organizational roadblocks Servant leaders
24. Stakeholders Anyone with interest on the project Not responsible but provide inputs Affected by the project’s outcome Provides regular feedback during the agile process
25. Agile Mentor Experienced in implementing agile projects Knowledgeable in agile approaches and techniques Provides valuable feedback Not responsible for executing product development
26. Roadmap to Value Stage 4: SPRINT PLANNING Stage 5: DAILY SCRUM Stage 6: SPRINT REVIEW Stage 7: SPRINT RETROSPECTIVE Stage 3: RELEASE PLANNING Stage 2: PRODUCT ROADMAP Stage 1: VISION PREPARATION EXECUTION
27. Events SPRINT DAILY SCRUM SPRINT REVIEW SPRINT RETROSPECTIVE SPRINT PLANNING RELEASE PLANNING PROJECT PLANNING
28. Artifacts Product vision statement Release Plan Product Backlog Product Roadmap Sprint Backlog Increment
29. Agile Methodologies
30. Agile Methodologies Crystal FDD
31. Scrum Product Owner works with team to identify and prioritize Cross-functional teams estimate delivery of increments One Sprint Backlog is committed, no additional functionality can be added to the Sprint One Sprint is delivered, the Product Backlog is analyzed and reprioritized if necessary
32. Kanban Visualize what you do today Limit WIP Enhance Flow
33. Lean Eliminating Waste Amplifying Learning Deciding as Late as Possible Delivering as Fast as Possible Empowering the Team Building Integrity In Seeing the Whole
34. XP Planning Game Small Releases Customer Acceptance Tests Simple Design Pair Programming Test-Driven Development Refactoring Continuous Integration Collective Code Ownership Coding Standards Metaphor Sustainable Pace
35. LOHICA SOFTWARE SOLUTIONS 2F #120 Cordillera St., Sta. Mesa Heights, Quezon City, 1114. +63 2 559 9441 consult@lohica.com www.lohica.com