Presented at Journée Agile 2017. Feedback on 5 Scrum projects in various environments, from the start-up to the tentacular administration. Some environments were amenable to agility, some were hostile.
We train our people to work in an agile way, and not do waterfall.” Me: “Good.” (to the junior candidate) “What were you contacts with other teams?” Candidate: “I worked often with the stakeholders to write user stories.” Me: “And did you meet the development team frequently?” Candidate: “No, not that much”
and roles ✗ Ignoring agile values and Scrum practices ✗ Pretext to skip specifications and documentation ✗ Large and/or single function team ✗ Traditional project management in disguise
as long as it works outside the Scrum perimeter ✗ No PO PM is no substitute for PO! Lack of PO can leave the team hanging dry PO/PM confusion leads… well, to confusion
for frustration by budget overshooting Leads to team bullying by PM to stick to bogus estimates Usual consequences: ✗ Demotivation ✗ Overwork ✗ Quality decrease ✗ Work avoidance strategies
queues) ✓ Limit work in progress (WIP) to avoid task switching and limit reprioritization ✓ Focus on Flow and collect metrics about it ✓ Pull work ✓ Continuous improvement to avoid one-size-fits-all syndrome
weeks ✗ DEV team has close to 0 automated tests ✗ DEV team has limited business knowledge to write tests ✓ but TEST has thousands of test cases! ✗ FA vs DEV vs TEST vs business → silos → no one collaborates
managers) ✓ All your tests are belong to us (Not to the TEST team only) ✓ Automate everything ✓ Self-organized team ✓ PM outside the perimeter made not harm
internet with no authors mentioned… Thank you. Cette œuvre est mise à disposition selon les termes de la Licence Creative Commons Attribution - Partage dans les Mêmes Conditions 4.0 International.
l’idée que le périmètre fonctionnel semble être fixé à l’avance par le client.” Claude Aubry, “Scrum - Le guide pratique de la méthode agile la plus populaire”, p. 260
provision ✓ Win-win provision ✓ No charge termination provision ✗ Inflated fixed price How do you “welcome” change in that context? Feasible, but does it make sense?
Agile and Scrum.” Me: “That’s great. You guys do retrospectives, reviews, and measure your velocity?” Customer: (unfazed) “No, we don’t do that. But we have posts-its and meet daily.” Me: “And your does your team work? Do you have testers and analysts in the team?” Customer: (embarrassed) “No, the testers belong to another teams, and analysts are in a separate team as well.” Me: “I see.” (awkward moment follows)
I hate it.” Me: “How comes?” Him: “It’s such a waste of time. Those daily stand-ups last forever, sometimes 40 min.” Me: (frowning) “But that’s way too long for the intended purpose.” Him: “Some often go into endless details that only matter to 2 or 3 people. But the Scrum master does not intervene.” Me: ‘’Your team should stop doing that. How is the team composed anyway?” Him: “We’re 14.” Me: “Fourteen? That’s way too much for a Scrum team!”
two developers actually.” Me: “Ouch. What does your Scrum master say about that?” Him: “He does not intervene. The Project manager needs these meetings for his reporting.” Me: “What? This is so wrong.” Him: “Yeah the worse are the black Thursdays, where we do only meetings, the whole day. And it serves no purpose, there is no actual decision, and people are unhappy.” Me: “Why are you doing it then?” Him: “It’s all politics. Doesn’t matter. We just ignore the whole thing, and do whatever is needed for the project.” Me: ‘’That’s absurd. But you know you’re not doing Scrum at all, right?” ...
method.” “There is no documentation, how do you want it to work?” “We’ve wasted too much time on reviews and discussions.” “There is no management. Everybody does what they want.” “There is no planning in your Scrum.” These are actual sentences I’ve heard. At least several times.