“Rescuing Scrum teams keeps me in business”
Oh boy, does this sound familiar. James Shore, consultant, lays down just how bad it gets when you ‘go Agile’ and don’t do so correctly: The Decline and Fall of Agile: Without continuous, incremental...
View ArticleDealing with technical debt
codeartisan: Jon Moore: Cracking down on technical debt: Generally, as the folks with the technical ability to recognize it, it is the development team’s responsibility to try to avoid accruing...
View ArticleMore on Bad Agile
Steve Yegge talks about Google’s development (circa 2006) process – a process that is focused on being agile – and riffs on just how bad “Bad Agile” can be: Good Agile, Bad Agile: Bad Agile hurts teams...
View ArticleTwo on project process
Aaron Held, coworker at CIM, “A House With No Front Door Keeps you off the streets”: Scrum and Agile are desinged to solve this by making it a team effort. So in Scrum it is not the “developers” that...
View ArticleSome light reading (and research) on non-functional requirements in Agile/Scrum
Agile Modeling: Introduction to User Stories Mike Cohn’s Blog: Non-functional Requirements as User Stories aqris: Representing non-functional requirements with user stories wikiwiki: Non Functional...
View ArticleAn introduction to Kanban
Jeff Patton put together an introduction to Kanban that has helped me become familiar with some of its concepts on his blog, AgileProductDesign.com, “Kanban Development Oversimplified”.
View ArticleOn Visualizing Iterative Waterfall
Go read Jon Moore’s latest piece “The Power of Visualizing Iterative Waterfall”: “the most powerful reason to start visualizing the flow is that it shows you exactly what parts of your process you...
View Article
