A PROJECT MANAGEMENT use case – AGILE
PROJECT MANAGEMENT use case – AGILE
Project Management (Any project) | Agile (Software) |
Adaptability and Resiliency | Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. |
Change | Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. |
Complexity | Simplicity--the art of maximizing the amount of work not done--is essential. |
Leadership | The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. |
Quality | Continuous attention to technical excellence and good design enhances agility. |
Risk | Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. |
Stakeholders | Business people and developers must work together daily throughout the project. |
Stewardship | At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. |
Systems Thinking | Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. |
Tailoring | Working software is the primary measure of progress. |
Team | The best architectures, requirements, and designs emerge from self-organizing teams. |
Value | Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. |
Comments
Post a Comment