Sublime

Manifesto Ágil”. Nele, declaramos os seguintes valores: indivíduos em vez de processos; produtos que de fato funcionem em vez de documentação dizendo como deveriam funcionar; colaboração com o cliente em vez de negociação com ele; e responder às mudanças em vez de seguir um plano.

Para cada sprint, Farbood priorizaba el trabajo que había que hacer aquel mes escribiendo una serie de «historias de usuario», una técnica del desarrollo ágil.

find out if you’re really doing CI, ask your team the following questions: Are all the developers on the team checking into trunk (not just merging from trunk into their branches or working copies) at least once a day? In other words, are they doing trunk-based development and working in small batches? Does every change to trunk kick off a build

This cascading delegation, shown in Figure 4-4, with alignment to the level above, borrows heavily from the lean movement’s Hoshin Kanri.5 In particular, the concept of “catchball” emphasizes communication, accountability, and feedback between layers of responsibility in the organization.

Ongoing progress updates,

A cada três semanas, as equipes precisavam mostrar para os colegas o que estavam fazendo.

Scrum is a technique used by engineers to commit to progress and hold each other both accountable and to support each other. Each week an engineer shares what happened last week, what they commit to doing next week, and any blockers that keep them from their goals.

This system is called agile development for a good reason: teams that employ it are able to change direction quickly, stay light on their feet, and be highly responsive to changes in the business requirements of the product owner (the manager of the process—in this case Farb—who is responsible for prioritizing the stories).