Nah Wee Yang about .me/wynah
§ Agile Concepts & Principles
§ Agile Practices
§ What’s Hot and What’s Cool
§ Open Discussions
Myths • Customer knows exactly what they want • Developers know exactly how to build it • Nothing will change along the way
Reality • Customers discover what they want when they see it • Developers discover how to build when they build it • Many things change along the way
IKIWISI I’ll Know It When I See It
AGILE
• Agile is a Philosophy or Mindset • Based on agile values, principles & practices • Agile Manifesto
– 4 Values – 12 Principles
AGILE CONCEPTS
• Learning Progression v first learn, then detach, and finally transcend
• Shu v Learn a technique that works
• Ha v Learn the limits of the technique
• Ri v Shift techniques at any moment
守
破
離 Alistair Cockburn, Agile Software Development: The Cooperative Game, 2nd ed. (Upper Saddle River, NJ: Addison-Wesley, 2007), 24.
AGILE MANIFESTO
• Individuals and interactions over processes and tools • Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan
Values 4
http://agilemanifesto.org
AGILE MANIFESTO
1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software
2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale
4. Business people and developers must work together daily throughout the project
Principles 12
http://agilemanifesto.org
AGILE MANIFESTO
5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done
6. The most efficient and effective method of conveying information to and within a development team is face-‐to-‐face conversation
7. Working software is the primary measure of progress
8. Agile processes promote sustainable development. Sponsors, developers, and users should be able to maintain a constant pace indefinitely
Principles 12
http://agilemanifesto.org
AGILE MANIFESTO
9. Continuous attention to technical excellence and good design enhances agility
10. Simplicity – the art of maximizing the amount of work not done – is essential
11. The best architectures, requirements, and designs emerge from self-‐organizing teams
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly
Principles 12
http://agilemanifesto.org
AGILE vs TRADITIONAL
AGILE vs TRADITIONAL
• Traditional: Known (fixed) scope; estimate time and cost
• Agile: Emerging (variable) scope; fixed cost & time if there is flexibility on scope priorities
§ Agile Practices
AGILE PRACTICES
Scrum: Provides an agile project management framework
XP: Focuses on agile engineering practices
Kanban and Lean: Limit work in progress and optimize flow
DSDM: Takes a broader stakeholder perspective on the team
FDD: Focuses on feature delivery
Crystal: Outlines situationally specific solutions
§ What’s Hot and What’s Cool
WHAT’S HOT
• Professional Certification o PMI Agile Certified Practitioner (PMI-‐ACP)® o Agile Project Management (AgilePM™) o Certified Scrum… Master, Professional, Developer, Product Owner (CSM, CSP, CSD, CSPO)
• Servant Leadership • Disciplined
WHAT’S HOT
• PMI-‐ACP® Exam Requirements
Education General Project Experience*
Agile Project Experience*
Training in Agile Practices
High school diploma or equivalent
2,000 hours (about 12 months) of project team experience within the last 5 years
1,500 hours (about 8 months) of agile project team or agile methodology experience within the last 3 years
21 hours
WHAT’S COOL
• Focus on frequent and early delivery of Value • Never “miss” the deadline again! • “User Stories” instead of Specifications • Whole Team • Self-‐Organized
§ Open Discussions
Let’s Talk …
A G I L E
Thank You Nah Wee Yang about .me/wynah
Recommended
