Best practices, lessons learned and advice from your peers in the trenches.
Story points are one of the most misunderstood and misused aspects of the Agile methodology. In the second installment of our series on Agile Anti-Patterns, we look at two more ways that story points can be used incorrectly, making the team both less agile and more frustrated in the process.
The best process for your project should be determined by careful consideration of key factors, including overall complexity, the level of risk involved, and time-to-market requirements. Often, a flexible hybrid approach fits best, but it must agreed upon by management and the team before the project starts.
The Pomodoro Technique is a popular approach to time management, and it shares obvious similarities with some ubiquitous concepts in Agile, Lean and Scrum such as timeboxing and sprints. But is it really a good fit for teams working in Agile environments, or is it better employed as a personal productivity tool?
In this new series, we look at some common problems that Agile teams face, and the common “solutions” that rarely seem to work and often make things worse. Sometimes we need to avoid the well-worn path. Let’s start with the misguided attempt to directly translate story points to effort hours.
A turning point in World War II, the D-Day invasion, code name Operation Overlord, offers a number of critical lessons that today’s project leaders would do well to revisit now and again, from the fundamental importance of clearly defined objectives and thorough training, to overcoming the unexpected and fully utilizing your strengths.
What are the pros (and potential cons) of applying psychological tools like social engineering, aikido and body language to your projects? Rachel Gertz, co-owner of training school Louder Than Ten, discusses how these concepts can be used by project managers to protect teams, connect with clients and ultimately deliver better results. [18:00]
In part five of our six-part series, we consider team structure and recommend a co-manager model that pairs the OPM with a client, business analyst or subject matter expert. This model facilitates meaningful stakeholder involvement while addressing the OPM’s challenges of juggling multiple responsibilities and sharing resources with competing priorities.
The most basic form of requirement in an Agile project is the User Story. It describes an actor, what the actor is trying to do, and the actor’s goals. Each story is unique, but they all should have the same components and adhere to the same guidelines. To make this happen, consider the acronym INVEST.
In this installment, we introduce an adaptable framework for Occasional PMs to use as a recipe or a starting point for managing their projects, regardless of classification or type. This framework allows the OPMs to control the project management process rather than having the process control them.
Metrics are easy to get wrong, and the price tag can be high for projects and stakeholders. Are your organization’s metrics providing value or just getting in the way of your team? Here are nine criteria for determining if your current metrics should be tweaked or removed, and if new ones would be more useful.