Through this, we have come to value:
Proper Scrum over working software
Undisturbed sprints over customer collaboration
Meeting sprint goals over responding to change
the items on the left are much easier to implement.
"My team mentioned the following: We are unable to focus on the work, resources are being borrowed mid flight, we have to wait for env to be ready for testing/deployment , priorities keep changing and worst of all ; often we hear <Our resources should give their 100%>, now how the hell can we give 100% with these constraints?"
|The NEAR Communication debt model|
|The 4 "Re" of Complexity|
|A simple CI chain, providing essential feedback to the developer|
blink()This small function snipped would allow me to set the color of our blink1 LED to anything I wanted, for example, red, blue - or green.
~/tools/blink1-tool "--$1" 2>&1 >/dev/null
fail()Of course, I'd also need a success state, which looked pretty much the same.
echo "CI step failure." | log
for task in checkout install_bundle clean_db run_tests; do
( succeed )
echo "$git_feedback" | log
[[ "$git_feedback" == "Already up-to-date." ]] && return 1
|A classic example of a hierarchy|
|Anarchy: The nightmare of every manager|
|In a holarchy, there is no "up and down" and no permanent structure.|
|An example Task Design Board|
|"I don't think it means ..." courtesy of memegenerator.net|
As a <ROLE> I want <FEATURE> so that <REASON>Some guys at Connextra figured out in 2001 that a good way of formulating user stories is with their template. It helped them solve their problem and now people make that a (near) essential part of Scrum.
|The process of making toast - which model is "right"? Mine! ... oh wait!|
|Toast? Close enough.|
|Left: About yourself. Right: About others.|
|Bored of yet another Good-Bad-Improve Retro? Good!|