Best practices, lessons learned and advice from your peers in the trenches.
Many project teams experience an occasional lapse in accountability — important work falls through the cracks — and sometimes the problem becomes a crisis. But what exactly is ‘accountability’, and how do we improve it? Here’s a helpful model based on constancy of purpose, aligned actions and discrete outcomes.
Do you tackle the most critical, high-profile elements of an initiative as early as possible or hold off until you have a better understanding of the end-game? Home improvement projects, Meryl Streep, and book writing offer insights into three common mistakes project managers make when planning workflow.
It can seem like a good idea to add a backup story into a sprint — if works gets blocked or things turn out easier than expected, another story can be pulled into the sprint. However, having more than one story identified, even if not committed, is likely to lead to less work getting done.
What’s the difference between a “strategic initiative” and a “project”? The question has sparked debate within the project management community. Here, IT strategist Erika Van Noort shares her thoughts on why it matters, and how a change in terms can reframe the mindset of everyone involved, leading to better results.
Sometimes success breeds failure. When project managers blindly apply old methods to new circumstances, they fall victim to the turkey problem. Assuming stability, they don't adapt new frameworks or solutions when warranted. Here are five ways to combine mastery and originality as you approach your next project.
Writing effective user stories on Agile projects requires collaboration between the product owner and team. The effort involves agreeing on the depth of technical detail in the story, ensuring that epics are appropriately broken down, and adding acceptance criteria. Let’s look at some helpful examples for each step.
There are many ways that story points are often used incorrectly by well-meaning teams. In the fourth installment of our series, we look at two more agile anti-patterns that seem like good ideas but aren’t: allowing everyone to have a vote, and playing “Go Fish” during planning exercises.
In agile projects, most requirements start out as epics, which are too big to be addressed in a single sprint. Let’s look at some examples of how epics are broken down into manageable stories through team and user collaboration, and how acceptance criteria add important details.
Requirements in Agile environments are handled very differently than in projects following linear processes. In Scrum, requirements are collected and shared through user stories, which have a precise format that invites conversation and collaboration. Here are some examples and guidelines for writing effective user stories.
Using story points for estimation seems simple enough, but many teams fall back on old habits without realizing that they are misusing one of the key innovations of the Agile methodology. In the third installment of our series, we look at two more agile anti-patterns: conflating story points with story value, and relying on an anchor story.