Articles, Blog Posts, Books and Quotes on Agile Project Management
There might exist some lonely standalone software developers that create software without any other person involved, but my guess is that there are not many of them. Communication is an essential skill in software development, testing and project management… and life. As feedback is a key communication tool, I was therefore very interested when I stumble on this book about feedback written by an Agile coach.
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.
If Scrum and Agile approaches are supposed to increase the chances of success for software development projects, not all the projects that want to use Scrum are successful. In some organizations, Scrum is a failure. This article discusses why Agile projects might fail because of the confusion between the Scrum roles (Scrum Master, Product Owner, Developer) of a Scrum Team and the required Agile mindsets.
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.
The ScrumMaster role might be the most difficult to define among the three roles involved in the Scrum team. Starting from a “bad” ScrumMaster job description, Agile coach Sam Laing discusses in this article the errors to avoid when you create a Scrum Master role specification. As a bonus, she provides at the end a good ScrumMaster job description.
Agile Open Florida is a conference organized by leaders and volunteers from the Agile Florida community who are passionate about building community and advancing all things Agile. Adam Sandman, whose company was also sponsoring Agile Open Florida 2016, has written his personal report about some of the sessions.
At the beginning of his book, Allan Kelly describes Xanpan as both a method and a philosophy, his philosophy on how software is, or should be, created, and how Agile works, or should work. If Xanpan is basically a mix of XP (eXtreme programming) and Kanban, it contains ideas and techniques of other Agile and Lean approaches, focusing on how teams should work together to deliver better software and value.
Scrum Expert Copyright © 2009-2024 Martinig & Associates