A sprint review is an essential part of the agile process, where the team can demo new features and functionality. But the demo is only half the story. The sprint review is also an opportunity for productive conversation and feedback between the team and stakeholder, which will lead to a better product.
Backlog refinement sessions offer many benefits, but there are also well-intentioned activities—or antipatterns— that can be detrimental to the team. Here are five backlog refinement antipatterns to avoid, from focusing on estimates to removing requirements too quickly.
Project leaders must cope with many uncertainties, from requirements to schedules. These uncertainties can’t be removed but they can me managed and often mitigated. Here are some strategies and actions to address risks, reduce ambiguities and retire unknowns.
Network:4424
Network:1390
Network:275
Network:1071
See all Requirements Management Influencers
Join us for PMI Business Analysis Virtual Conference 2019! This virtual event will explore the latest trends in business analysis and provide you with the insights, resources, and tools to advance your career and enhance project success.
Over the years business analysis has continued to grow at a rapid rate and is often seen as a critical leadership competency for Projects, Programs, and Portfolios. Business Analysis provides important value by reducing project costs and increasing the potential return, or benefits. This PMI virtual event will provide insights on just how critical of a role business analysis plays in the overall success of project while giving you the BA insights, resources, and tools you need for total project and career success.
If you perform business analysis, your work is vital to project and program success. To most effectively support your organization and advance in your career, you need to know how to apply BA to any situation and delivery method. The new PMI Guide to Business Analysis will help you achieve this! Get an exclusive preview, with in-depth insights, at the PMI Business Analysis Virtual Conference 2017.
In this three-part podcast, Laura Paton, MBA, PMI-PBA, PMP, CBAP, CSM, the lead author of PMI’s Business Analysis for Practitioners: A Practice Guide, discusses elicitation and analysis techniques for business analysts, as well as the new practice guide and who will benefit from it.
In this three-part podcast, Laura Paton, MBA, PMI-PBA, PMP, CBAP, CSM, the lead author of PMI’s Business Analysis for Practitioners: A Practice Guide, discusses elicitation and analysis techniques for business analysts, as well as the new practice guide and who will benefit from it.
In this three-part podcast, Laura Paton, MBA, PMI-PBA, PMP, CBAP, CSM, the lead author of PMI’s Business Analysis for Practitioners: A Practice Guide, discusses elicitation and analysis techniques for business analysts, as well as the new practice guide and who will benefit from it.
Many times, project managers are not sure what that next step should be after they earn their Project Management Professional (PMP)® certification. In this webinar, we will describe several possible career paths based on our experience and share tips on how to get started.
All of us know about business processes. Any business development starts with a process organization. Before starting a new project, we also have clearly defined processes and a clear understanding of these processes. We have these processes groups in each project. We need the system approach for the project execution. Understanding Project Management processes in the context of the organization's business processes is very important. It'll help us apply various Project management methodologies, and their effective combination, as well as it gives the possibility of flexible management. This webinar will show a point of view, answering the following questions. Which business processes are we have in the project? How to effectively integrate the project management processes into the business processes of the organization? What could we do for their evolvement?
A new collaborative blog featuring the contributions from the core team members of PMI's Foundational Standard in Business Analysis. This blog will provide the community with insight into PMI's development of the standard to generate professional discussions about the content in advance of the scheduled reviews.
Effective requirements collection, management and traceability plus smart PM practices equals project success.
Start your requirements gathering with this all-inclusive document outlining the entire process from start to finish.
The System Requirements Specification (SRS) document describes all data, functional and behavioral requirements of the software under production or development.
This deliverable aligns with the concepts expressed in the article Strategic Requirements Management. This template should be used in conjunction with a more traditional requirements document to assist in the prioritizing of features and the finalizing of scope elements. It can also support discussions around changes in scope during the project. The cells below provide a basic summary of each column.
The Requirements Management Plan is primarily used for communications, giving all stakeholders a view on how this process is managed for your project. It completely answers the very common question, "How are you identifying and managing your project requirements?"
Even a small change can have a huge effect on a project. This impact analysis study will help you measure the effect of a potential change on your project's scope.
This planning guide will help you with the review and selection of project requirements to be included in the current scope. All requirements candidates are captured here, along with some basic information about them. Each candidate is then scored based on a number of different factors. The completed template provides a validation that the requirements ultimately approved are the ones that are the most appropriate for inclusion.
The primary purpose of this document is to track the status of change requests that have been created on the project. For smaller projects or projects where the scope is well defined, the log may not be useful. For larger, more complex projects, or for those projects where there is a lot of change, a change request log can be very useful.
The project scope statement details your project's deliverables and describes the major objectives, which includes measurable criteria for success. Use this template to document the six essential elements.
We can’t schedule innovation, but we can schedule and fund discovery—an essential part of building products that matter. How do we make the case for discovery as the true path to innovation? Make it tangible and frame it in non-specialist language.
Many project practitioners focus on execution and think their responsibilities start with the kickoff meeting. But before then, a good intake process can ensure a project is truly ready to begin. And, yes, it should involve not just portfolio or program leaders, but also project managers and teams.
To build better applications, citizen developers need to learn how to analyze and design for enterprise risk requirements as a part of capability development.
In agile product development, we try to work on fewer things and stick with them until we finish. Rapid priority shifts are expensive and demoralizing. But that’s not always clear on the go-to-market side, so we need stories like the Hungry Man Parable to build better understanding.
Scope creep can plague projects where timelines are established at the start, or budgets and resources are fixed. However, it should not be a problem for projects operating with agile principles. Rather than resisting change, an agile team welcomes it, and figures out how to adapt to it. Here's how.
Question: Last week, I was told that there will now be a business analyst (BA) working with my project team. To be honest, we have all the roles filled. Why are we being assigned yet another person to deal with? Isn’t it enough that they also want us to work with a second team to produce the tangible portions of this project, while we do the software and other soft deliverables? Can I refuse to accept this person into the group?
Faced with a project that had no defined scope and no project manager, this practitioner took on the role. Since then, he has completed dozens of similar projects and worked out a reliable general process with five steps.
Experience in the delivery of programs and projects addressing many aspects of emerging technology disruption is virtually non-existent. How will you manage the delivery of these strategic initiatives that include new and unfamiliar technologies?
Organizational leadership often favors the development of soft skills, resulting in the gradual erosion of PM technical skills that form the foundation of any solid project management capability.
Having worked as a project manager delivering technology solutions to life sciences clients for close to a decade, this author has noticed common themes that help ensure project success. Here are six project management takeaways from delivering projects to regulated companies.
Ask a Question |
Discussion Rules |
