| A | B |
|---|
| Agile Manifesto 1 | Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to a shorter timescale |
| Agile Manifesto 2 | Working software over comprehensive documentation |
| Agile Manifesto 3 | The best architecture, requirements, and designs emerge from self-organizing teams |
| Agile Manifesto 4 | Continuous attention to technical excellence and good design |
| Agile 1 | Failure: Fast and Early |
| Agile 2 | Product Development: Iterative and Frequent |
| Agile 3 | Reduced development risk. Lower defect density |
| Agile 4 | Greater visibility, communication, trust between IT and Business |
| Product Owner 1 | Visionary, requirements source, decision maker |
| Product Owner 2 | Responsible for being a liason between the client's business stakeholders, sponsors business SMEs and scrum team |
| Product Owner 3 | Visionary, requirements source, decision maker |
| Product Owner 4 | Is a key role for agile to be successful |
| Scrum 1 | Enabling fast feedback, continual improvement |
| Scrum 2 | Shorter time-boxed schedules |
| Scrum 3 | Produces key artifacts: Product backlog, Sprint backlog, Release Backlog |
| Scrum 4 | Only has three key roles |
