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?
In this interactive and engaging talk you will learn about some of the principles that have led the Technology Innovation and Consumer Experience team at Thomas Jefferson University and Jefferson Health System to analyze, design, develop, release, evaluate, and support innovative enterprise applications with small teams in less than 30-days.
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
This series provides valuable information for the product owner community to use additional good practices in their projects. In each installment in this series, 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 installment looks at business data diagrams.
Is agile the tsunami of change? Not necessarily, but the wave of change is coming to our profession. This practitioner warns that it won’t hit us like a waterfall—it will hit us like a tsunami. Will you be ready?
The agile approach needs to be understood thoroughly before it is introduced to a company. This explanation will give leadership the information they need for deciding if agile project execution is right for their organization by discussing key points including core framework, high-level benefits, and risks in the project-based environment.
When should you use waterfall and when should you use agile? The usual answer to this question is vague: Apply each approach according to circumstances. This article discusses the main positive and negative aspects of the waterfall and agile approaches, deconstructing some of the myths behind them and suggesting where one could be used over the other according to different factors.
This series provides valuable information for the product owner community to use additional good practices in their projects. In each installment in this series, 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 edition looks at the business objectives model.
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.
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.
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.
Ask a Question