Articles on Scrum and Agile Project Management
“Swarming” is a technique whereby many members of a Scrum team work together to deliver a User Story, taking advantage of the skills of many team members together. In this article, Johanna Rothman asks the question: How do you do swarming in a distributed team?
In this article, Brian Vanderjack shares 21 ways to engage and retain the product owner in a Scrum project. The Product Owner role is very important in Scrum, because he guide the team on how to add business value through creating, prioritizing and managing user stories. Thus it is a big problem when the Product Owner is only involved and not committed to the project.
Paul Pazderski proposes in this article a scorecard to assess the level of transformation of a project team into a Scrum team. This card could be filled by an independent observer like an Agile coach to check how the team is adopting Scrum practices like Product Backlog management or Sprint Reviews.
In this article, Mitch Lacey discusses the difficulty faced when trying to provide estimates for software development project. The beginning of a software project is the time when you are the least certain about the final scope project, but it is also when you are asked to deliver precise estimates. Agile tries to move from uncertainty to certainty in as quickly as possible.
In this article, Faisal Mahmood discusses seven reasons why a Scrum team cannot get to done at the end of a sprint. In Scrum, “done” is often defined as producing a potentially shippable product.
In this excerpt of their book, Sam Guckenheimer and Neno Loje describes the mechanisms that Visual Studio (primarily Team Foundation Server [TFS]) provides to support the team enacting an Agile process. This article provides an inside-out overview of what makes the enactment of Agle possible in Visual Studio.
This article from Rob Maher focuses on how to increase productivity. It discusses how changing a project staffing model could increase the productivity of project teams (PDF document). There is published evidence that short-lived groups of people brought together for a project are correlated with lower productivity. His view is that in an agile world, teams are permanent and the organization optimizes at the team level. Permanent teams enable consistent estimation, which is not possible using the matrix approach.
Scrum Expert Copyright © 2009-2024 Martinig & Associates