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
Today, roles have changed. As a project manager, you must keep your projects (and developers) on the right track. It doesn’t matter how many languages or platforms you know. This seasoned practitioner explores two different approaches and applies them to a complex IT scenario, looking at the best of both worlds.
For many, the concepts of agile are distinctly related to software development. But there has been a trend over the past 15 years of agile approaches taking root outside of software development and systems integration projects. Agile has not only appeared outside of its usual places, it has thrived in many of these new areas.
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.
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.
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?
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.
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.
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.
Ask a Question