Bob Hartman, from the Agile for All blog writes about the agile antipatterns insanity – continue doing the same things that always fail, thinking they will work better the next time without changing anything. I agree with every word, especially with the pattern of testing late, and code freezes during each iteration I see this …
InfoQ: Pulling Power: A New Software Lifespan tags: lean, design, agile, agileblog how Kanban metaphor from Lean manufacturing and the Feature Injection template play into Behaviour Driven Development, working together to help us identify the most important software, reduce unnecessary artifacts at each stage of development, and produce the minimum necessary to achieve a vision …
great Kanban Parable tags: kanban, parable, agileblog Posted from Diigo. The rest of my favorite links are here.
A key theme in Agile is embracing change. We hear time and again that change is good, we should “welcome change”, yada yada yada. Most teams I see are sick of change. On one hand they are not fully exposed to the business case for change, to the sense of urgency around changing fast. On …
kanban-for-software-engineering-apr-242.pdf (application/pdf Object) Comprehensive write-up of Lean+Kanban. Heavy but worth reading tags: agileblog, lean, kanban Posted from Diigo. The rest of my favorite links are here.
Scrum/Agile Projects introduce several challenges/forces that are easier to deal with when leveraging agile engineering practices. On a daily basis I see teams struggling with questions around how their engineering practices are compatible, or most of the time incompatible, with the Agile mindset. These teams face two options – Either improve their engineering practices so …
Goals for using Kanban tags: kanban, agileblog Goals for using Kanban Goal 1. Improved performance through process improvements introduced with minimal resistance Goal 2. Deliver with High Quality policies around what is acceptable before a work item can be pulled to the next step in the process focus on quality by limiting work-in-progress Goal 3. …
Goals for using Kanban tags: kanban, agileblog Goals for using Kanban Goal 1. Improved performance through process improvements introduced with minimal resistance Goal 2. Deliver with High Quality policies around what is acceptable before a work item can be pulled to the next step in the process focus on quality by limiting work-in-progress Goal 3. …
Can you tell off the top of your head (or via a simple query in your issue tracker) what is the regression ratio in your product for a specific version, and where are the regression areas?Chances are, the answer is no. The reason is that out of the box, most issue trackers don’t indicate an …