Articles, Blog Posts, Books and Quotes on Agile Project Management
Marc Löffler shares in this blog post 11 hints to improve all the Scrum meetings. He discusses daily stand-up meeting where he suggests to show colleagues what your currently working on instead of just talking about it. He also make proposals to improve the sprint planning, sprint reviews and retrospectives.
In this blog post, Michael Sahota explains the basic principles of NonViolent Communication (NVC) and how they can help your to improve communication in your Scrum team. Nonviolent communication (also called compassionate communication) is a communication process that often functions as a conflict resolution process. It focuses on two aspects of communication: honest self-expression and empathy. This communication is very close to the concepts developed in the Core Protocols.
Henrik Larsson presents in this post the user stories lifecycle from their origin in a Minimum usable feature (MUF/MMF) to their validation by the product owner at the end of a Scrum sprint.
In this blog post, Marc Löffler shares a checklist of items and best practices that should facilitate the a successful retrospective for a distributed team. Even if virtual retrospectives are fine, he suggests that distributed team should meet personally on a regular basis, if possible every two retrospectives.
This article describes an emerging enterprise pattern for the successful implementation of software agility at the project team, program and portfolio level. It describes the new software development and delivery process mechanics, the new teams and organizational units, and some of the roles key individuals play in the new agile paradigm. In addition, the Big Picture highlights the requirements practices of the enterprise agile model, because they uniquely carry the value stream to the customer.
In this blog post, Sten Johnsen discusses the impact of moving uncompleted user stories from one Scrum sprint to another. He focuses on the unfinished user stories, its impact on the team velocity and its influence on the ability of the team to change.
“An adequate ScrumMaster can handle two or three teams at a time. If you’re content to limit your role to organizing meetings, enforcing timeboxes, and responding to the impediments people explicitly report, you can get by with part time attention to this role. The team will probably still exceed the baseline, pre-Scrum expectation at your organization, and probably nothing catastrophic will happen.
Scrum Expert Copyright © 2009-2023 Martinig & Associates