Other agile methods
Extreme Programming, Lean applied to software, Scrumban, Crystal, FDD, DSDM and agility at scale (SAFe): the central idea of each method, what sets them apart and when to choose them.
- 25 cards
- 4 topics
- Free
The outline, topic by topic
Each topic is weighted the way the exam weighs it.
- Concepts
- Questions
- Sort and link
- Scenarios
A few cards from the deck
Extreme Programming (XP): what is it?
Show the answer
An agile method centred on engineering practices: pairing, tests written first, continuous integration, code refactoring, very frequent releases.
Scrum organises work without saying how to code; XP says how to keep code quality high despite frequent changes.
A Scrum team wants to add engineering practices (tests first, continuous integration, refactoring) to its events. Which method gives them?
- Extreme Programming
- DSDM
- SAFe
- Scrumban
Show the answer
Extreme Programming
XP is the method of programming practices. DSDM manages time and priorities, SAFe coordinates many teams, Scrumban adds a pull flow: none prescribes how to code.
The values of Extreme Programming are communication, simplicity, …, courage and ….
Show the answer
The values of Extreme Programming are communication, simplicity, feedback, courage and respect.
Feedback comes from tests, continuous integration and the customer. Courage is, for example, refactoring working code to keep it healthy.
Lean software development: what is it?
Show the answer
An adaptation to software development of the Japanese production system, based on seven principles including eliminating waste, learning fast and delivering as fast as possible.
It looks at the value stream end to end: anything that adds no value for the customer is waste to remove.
Eight Scrum teams each deliver at their own pace and their work does not fit together. What is the cause, and what should be done?
- The teams are too small: merge all eight into one single large team
- The sprints are too short: move every team to sprints lasting a whole quarter
- The teams lack direction: a project manager should dictate all their tasks
- No cross-team synchronisation: adopt a common cadence (Scrum of Scrums, SAFe)
Show the answer
No cross-team synchronisation: adopt a common cadence (Scrum of Scrums, SAFe)
A product built by several teams needs common integration points. A team of over ten people no longer works well, and a quarter-long sprint or orders from above go against agility.