|
You are here |
jdavidcarr.com | ||
| | | | |
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. | |
| | | | |
anthonysciamanna.com
|
|
| | | | | Issues with user stories are a common problem for software development organizations that adopt agile frameworks. At some point in their journey develop... | |
| | | | |
theitriskmanager.com
|
|
| | | | | A month ago a colleague of mine asked me about stakeholders in Agile. After a moment of thought I told them that there are NO STAKEHOLDERS in Agile. What is a stakeholder? In traditional development, someone puts together a business case, some business value that will be delivered, often with a high level description of... | |
| | | | |
blog.ploeh.dk
|
|
| | | How do you know that your code works? | ||