/explore
|
You are here 
|
coreydmccarty.dev | ||
| | | | |
www.wagslane.dev
Let's discuss why I generally prefer Kanban to Scrum |
|
| | | | | ||
| | | | |
friendgineers.rosenshein.org
Biases blind us to choices. Usually without us even knowing it. No matter how boolean a computer is, the world is an analog place, and things are on a continuum. Our choices should acknowledge that fact. |
|
| | | | | ||
| | | | |
waldo.jaquith.org
When writing about Agile software development, I always capitalize the word. This isn't an affectation, but instead an effort to communicate an important distinction. |
|
| | | | | ||
| | | | |
sboots.ca
"Agile" gets mentioned enough in digital government work that can sometimes seem like it applies to everything: is anything not agile? But there's a deeper meaning behind it that's easy to miss: adding agile practices without removing established, "waterfall" processes that slow a team down is a recipe for frustration. Being agile means choosing one approach over another, and deliberately prioritizing what you spend your time on. |
|
| | | |||
