The reality is that projects are continuously failing due to the questionable process being executed to plan how to elicit, gather and document requirements. Many organizations are not spending time to plan for requirements development. Therefore, it begs the question: Is requirements planning a must?
Extreme projects feature high speed, high change, high complexity and high stress. As more projects continue to fall into the extreme zone, successful project and program managers will shift from inhibiting change to proactively creating change and responding to change.
Save Time With Tools And Templates
This presentation looks at a brief history and a definition of agile project management; looks at factors that affect selection of collaboration tool-sets; and looks at key features of project portfolio management tool-sets and at making PPM a business process.
Learn From Others
Most organizations struggle to engage their workforce to its potential. This is not through a lack of planning, technical skills or resources, but instead effective tools for dealing with typical project problems. Fortunately, agile practices hold many practical solutions for solving the classic five dysfunctions of a team.
Many organizations are obsessed with getting things done quickly no matter what. Therefore, they create reward plans that motivate this behavior. ScrumMasters gradually deprioritize promoting Scrum values and metamorphose into agile project managers. How can we prevent this?
This series provides valuable information for the product owner community to use additional good practices in their projects. In each installment, we take one of the most commonly used visual models in agile and explain how to create one--and how to use one to help build, groom or elaborate your agile backlog. This entry looks at the feature tree.
What does “scaling agile” mean to you? There are two ways to think about scaling: one is moving from one project to a program, the other is sharing agile across the business. Here we talk about moving from a one-team project to agile programs.
This fourth installment of articles scrutinizing agile frameworks based on values, principles and practices focuses on commitment (following the entries on courage, focus and openness). A stated value of the Scrum framework, commitment is everything in agile.
Today’s project delivery environment is more complex than ever—more projects, more complex projects and more varied projects than ever before. Does this environment still lend itself to a single methodology? And if not, what should an organization’s approach be?
All agile frameworks may be examined in terms of core values. This third entry in a five-part series continues to explore agile frameworks from the vantage point of values, principles and practices. Agile’s Scrum framework in particular espouses five values: courage, focus, openness, respect and commitment. This offering looks at the value of openness to bring principles and practices into better relief.
This series provides valuable information for the product owner community to use additional good practices in their projects. In each installment, we take one of the most commonly used visual models in agile and explain how to create one—and how to use one to help build, groom or elaborate your agile backlog. The first in this series is the process flow.
Do you know what expertise you need now, as you enter into an agile development environment? Unfortunately, we use the same word (“testing”) in agile, but it means something different from what you have seen and managed in prior non-agile projects. If your testers are writing test cases, tracking testing progress and recording bugs in a separate defect tracking system, stop now; you are using the wrong people to do the wrong thing.
|A.||Metrics or concrete, short-term data about the performance of each person working for an organization are crucial to make sure that team members are not slacking off and occupying a position someone else could use to bring the company more value.|
|B.||The new boss is trying to make his or her mark by introducing the new metrics to have something concrete to show. These statistics will prove to not be a good idea over time, so let the organization figure it out for itself. Collecting them is the equivalent of the lion’s roar to mark this territory to all within earshot.|
|C.||Only people who are fearful of what the data will show will object to having it collected, formed into charts and submitted to management. In fact, since you know what is being gathered you can change your daily performance to be sure you look good in these new metrics regardless of whether or not it is the best use of your time.|
|D.||An organization should look at the need for and value received from any metrics gathered and used. Unless they are collecting data that is meaningful and will lead to better results, they are a waste of company time and resources, may be misleading and may be discouraging for the team.|
Ask a Question