html5-img
1 / 190

Agile Project Management

L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n. Agile Project Management. L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n. Pollyanna Pixton Founder, Accelinnova President, Evolutionary Systems Director Institute of Collaborative Leadership.

duer
Télécharger la présentation

Agile Project Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n Agile Project Management

  2. L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n Pollyanna Pixton Founder, Accelinnova President, Evolutionary Systems Director Institute of Collaborative Leadership

  3. Agenda • What is Agile • Agile Methods • Scrum Deep Dive • Estimating and Planning • Getting Started • Leading Agile

  4. What is agile?

  5. “Find your joy in something finished, and not a thousand things begun.” - Douglas Mallock

  6. Project Methods • Waterfall: • Function Definition, Design, Build, Check Functions Design Build • New Methods: • Single Cycle Review and Adjust • Spiral: Multiple Cycles of Waterfall • Agile: Adapt As You Go: Short Iterations Check Done

  7. What is Agile? From recognition and acceptance of increasing levels of unpredictability in our turbulent economy • A chaordic perspective • Collaborative values and principles • Barely sufficient methodology - Jim Highsmith

  8. Agile Encourages Mid Course Corrections Zone of success Planned Completion Increasing Knowledge Planned Path Start Actual Path As Knowledge increases Leaders use iterations to guide project towards enhanced goal Actual Completion 8

  9. Business Driven – Faster & More Rewarding Staged Releases Profit Breakeven Breakeven Self-Funding Single Release Cost Software by Numbers by Mark Denne and Jane Cleland-Huang Agile projects have a break-even point earlier in time than a traditional waterfall project for applications of the same size. Agile projects are more flexible. Can be stopped or restructured without losing all value. Investment Time

  10. Agile Defined…

  11. uses continuous stakeholder feedback

  12. uses continuous stakeholder feedback principles end users partners insiders

  13. …to deliver high quality, consumable working code/features

  14. … through user stories

  15. …and a series of short, stable, time-boxed iterations.

  16. Agile Defined… Uses continuous stakeholder feedback to deliver high-quality, consumable code through user stories and a series of short, stable, time-boxed iterations.

  17. What is Agile? • A development process that conforms to the values and principles of the Agile Alliance(agilealliance.org) • Originally for software development

  18. Agile Manifesto While there is value in the items on the right we value the items on the left more. • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan

  19. Agile Overview Agile: • Iterative and Incremental to deliver working software • Light-Weight • Meets Changing Needs of Stakeholders • Highly Collaborative: Involves Customers • Minimizes Documentation • Test First

  20. Example: Legacy Highway

  21. Agile Principles

  22. Light Weight • Utilize only practices that make sense for the project and environment • “Barely sufficient” artifacts, methodology, and documentation • “Appropriate” vs “Best Practices”

  23. Practice Excellence • Requires self discipline to improved quality • Relies on the team to practice technical excellence instead of imposing discipline • Adopt technical practices that support the other practices such as: • Continuous Integration • Test Driven Development • Refactoring

  24. Reflect and Adapt • Learn from past to improve performance • Retrospectives after each iteration • Harness change for improved efficiency • Multi-Horizon planning allows adaptation

  25. Key Characteristics of Successful Agile Projects • Short, Stable, Time-Boxed Iterations • Stakeholder Feedback • Self-Directed Teams • Sustainable Pace

  26. The Process Pendulum Code and Fix Agile Waterfall No Process Empirical Prescriptive • Empirical • Frequent inspection • Collaboration • Adaptive responses • Prescriptive • Defined set of steps to follow • Plan the work, work the plan • Plan is assumed to be correct

  27. Project Methods • Envision • Iterate: • Plan • Implement • Done? • Adapt • Complete Project Definition and Iterations Planning Review and Adjust Implement NO Done? YES Completed Deliverables

  28. Agile Cycles Iteration Planning Vision Iterations Plan Iteration Plan Review / Adapt Planning Develop High Level Planning Detailed Planning

  29. How Does Agile Work? “Requirements” called features, defined using user stories: As a <user/role> … I want to <goal> … so that <value>.

  30. Agile ‘Process’ • User stories listed in a backlog. • Backlog prioritized based on value. • Highest priorities estimated and grouped into an iteration (sprint), two weeks long. • At end of iteration, ask if enough value to go to market? • Add any new user stories to backlog and reprioritize and select next iteration/sprint.

  31. Agile ‘Process’ • Test cases are written first, before anything is developed • Go/no-go decisions reached early and often

  32. Agile MUST be Disciplined Agile development necessitates greater discipline than traditional methods. “Quality” and “Consumability” must be real, not platitudes.

  33. “It is a bad plan that admits to no modifications.”-- Publius Syrus (ca. 42 BCE) Project Management

  34. What is agile Summary

  35. Agile Defined… Uses continuous stakeholder feedback to deliver high-quality, consumable code through user stories and a series of short, stable, time-boxed iterations.

  36. References • What Is Agile Software Development? Jim Highsmith, CrossTalk, the Journal of Defense Software Engineering • The New Methodology, Martin Fowler http://martinfowler.com/articles • http://www.agilealliance.com/articles • Why Agile (video) http://www.universite-du-si.com/fr/conferences/6/sessions/909

  37. User Stories Your Questions?

  38. Project Management • Remove Obstacles AgileMethodologies

  39. Agile Methods • eXtreme Programming, XP(Kent Beck, Ron Jeffries, Ward Cunningham) • Scrum(Jeff Sutherland, Ken Schwaber, Mike Beedle) • Feature Driven Development, FDD(Peter Coad, Jeff DeLuca) • Crystal Methods (Alistair Cockburn) • Dynamic Systems Development Method, DSDM (DSDM Consortium) • Lean Development (Bob Charette, Mary and Tom Poppendieck)

  40. Agile Overview “Agile projects succeed when the team gets the spirit of agility.” – Ron Jeffries, XP Thought Leader

  41. eXtreme Programming

  42. XP Values and Principles • Communication • Simplicity • Feedback • Courage • Quality Work

  43. XP Practices The Planning Game Small Releases Metaphor Simple Design Refactoring Test-First Development

  44. XP Practices Pair Programming Collective Ownership Continuous Integration Sustainable Pace On Site Customer Coding Standards

  45. XP Roles • The Customer Sets project goals and makes business decisions • The Developer Turn customer stories into working code • The Tracker Keeps track of any metrics used by team • The Coach Guides and mentors team

  46. Scrum

  47. Scrum Roles • Scrum Team • Scrum Master • Carries water and moves boulders • Product Owner • Responsible for maintaining product backlog

  48. Scrum Control Points Meetings: • Sprint Planning • Daily Scrum • Sprint Review(retrospectives and demo)

  49. Feature Driven Development (FDD) Model-driven short-iteration process that consists of five basic activities: Develop Model Build Feature List Plan By Feature Design by Feature Build By Feature Deploy - Jeff deLuca, 1997

  50. FDD Focus • (Object) Modeling centric • Client centric • Architecture centric • Pragmatic • Functional decomposition • Subject Area • Business Activity • Business Activity Step

More Related