Scrum and Kaban are two Agile approaches that could be used in software development, depending also on the context of the software development tools. In his blog post “Ditching Scrum for Kanban — The best decision we’ve made as a team”, Grant Ammons shares some thought on why he successfully changed it process from a Scrum to a Kanban perspective.
Blogs on Scrum and Agile Project Management
Having a good Definition of Done (DoD) might be one of the most important technical asset of a Scrum team. This makes the difference between delivering at the end of the sprint fully completed business features or half-baked software. In his blog post “Changing the Definition of Done”, Ken Rubin discusses the situation where a Scrum team might want to change an existing Definition of Done.
Technical Debt is defined as the eventual consequences of poor or evolving software architecture and software development within a codebase. In a blog post published for the Software Engineering Institute (SEI), Robert Nord has provided the keys points discussed in a seminar Managing Technical Debt in Software Engineering, an event that discussed both the past and the future of managing technical debt.
Metrics are an important part of Agile project management approaches like Scrum. One of the most used measures to estimate the amount of work are the story points. In this small article, Pedro Gustavo Torres explains what they are, why you need them and how to use them.
Using an Agile approach for software development does not necessarily guarantee success. As Henrik Kniberg wrote at the beginning of his blog post ” Even if the entire organization is neatly organized into scrum teams, you can still end up with an unaligned mess!”. Having an Agile leader can help preventing the unaligned mess.
The frontier is somewhat thin between analyzing things for continous improvement in Agile and blaming people for failure. In this blog post, John Allspaw discusses how Etsy wants to consider mistakes, errors, slips or lapses with a perspective of learning. he explains how having blameless post-mortems on outages and accidents are part of this approach.
Story mapping is a technique invented by Jeff Patton that order user stories along two independent dimensions. The “map” arranges user activities along the horizontal axis in rough order of priority. On the vertical axis, it represents increasing sophistication of the implementation. In his blog post, Sunit Parekh explains how you can apply story maps to build your product backlog in a visual way.