Best practices, lessons learned and advice from your peers in the trenches.
Changes, even when they are for the better of your project, come at a price. But it can be difficult to measure the true cost. Let’s look at five types of costs that change can bring to a project, from time to teams, and what we as project managers can do about them.
The Occasional Project Manager must first determine the type of project they are managing in order to choose the best approach. In part two of our series, we look at three types of projects that OPMs are most likely to encounter, and the unique challenges each presents.
In a follow-up to an article on backlog grooming, we answer reader questions about how the process differs from requirements documentation; how prioritization works without a complete picture; how a backlog differs from a work breakdown structure; and how to achieve an “all-in” view of product features when the backlog is a work in progress.
You can't build realistic forecasts without taking into account potential risks. So when it comes to creating project schedules, why is risk so often addressed as a separate exercise? To properly accommodate for uncertainty we need to embed and intertwine these processes within our tools. We need risk-adjusted scheduling.
In this new series, we address the Occasional Project Manager, a professional found in thousands of organizations, working on a variety of initiatives with minimal guidance. A majority of OPMs have no interest in a project management career, which is why they need an adaptive framework that applies to their work realities.
The OODA Loop is a concept used by military strategists and law enforcement to “get inside” an opponent’s decision-making cycle. Here’s how the technique can help to keep your projects in control — or to bring troubled initiatives back on track before it’s too late.
By understanding and adapting to different communication styles among team members, project leaders can provide all-important clarity on goals and expectations. And less confusion usually translates into greater team harmony and productivity. Here are four common communication styles and how you can work best with each.
The process of refining requirements to the point that they are ready to be worked upon is known as ‘backlog grooming.’ But this task accomplishes more than clarifying requirements; it informs stakeholders, contributes to the project plan, and reinforces Agile principles in general. Here’s guidance on how and when it should be done.
Management decisions made before a software project is underway are a significant factor in determining whether it succeeds or fails. Here are seven principles, based on comprehensive studies, that leaders must support and uphold to help create an environment in which projects can succeed. Ignoring them practically guarantees failure.
Few project management practitioners haven’t heard about Scrum by now, but many of those outside the software development arena are still seeking guidance about if and how its core concepts can help them avoid roadblocks and improve project outcomes. Here is a primer on the essence of what makes Scrum tick.