PM principles state that there should be absolute clarity in obtaining the requirements. If the fog of ambiguity clouds this phase, the delivered project will never be accepted by the stakeholders. Here we examine some of the glaring issues in the requirements management process.
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?"
Three core requirements management tools can effectively improve project management success: building a requirements tree, creating a requirements traceability matrix and establishing a requirements baseline.
The second State of Requirements Management Survey, sponsored by Ravenflow and Jama Software, is open through December 10, 2010.
Requirements management can mean many things to many people. For some it is about managing scope creep, for others it is all about traceability from definition through implementation. With that in mind, let’s explore some of the issues and challenges currently confronting effective requirements management.
Project leaders rush or minimize the requirements management process at their own peril. However, if we spend too much time on requirements, we are at risk of creating a burdensome process that will delay the project. It is important, then, to apply the appropriate amount of requirements rigor to our projects.
Results from a survey offer business analysts, project managers, developers and other project stakeholders information to help transform the way they produce and manage software requirements.
It is not uncommon to hear deadline-stressed project managers and team members rationalize about why requirements management is not necessary. But short-changing business analysis activities is one of the leading causes of rework and delays.
Today’s business realities demand a better balance of soft and technical skills from business analysts, according to a global panel of senior executives and consultants asked to identity the Top 10 Trends for the discipline.
How does requirements management fit into a project management framework? Here is an overview of the knowledge areas in the Business Analysis Body of Knowledge (BABOK), and their relationship to the project management plan as described in the Project Management Body of Knowledge (PMBOK).
The practices presented in this article--to build a requirements tree, create and use a requirements traceability matrix, and manage to requirements baselines--will make a significant difference in an organization’s success rate and promote improved partnership and standing within the enterprise.
Projects benefit from tools that promote communication and collaboration among stakeholders and team members. By increasing understanding of goals, priorities, issues and expectations, tools such as Microsoft SharePoint also help to identify — and eliminate — areas of duplication, improving productivity.
It is well known that agile projects work through prioritized lists of features, but the prioritization approaches available to us are not so well known. Here, we take a whirlwind review of popular prioritization schemes.
Here’s our February 2011 roundup of the latest technology solutions for project leaders, teams and organizations, including social-based requirements management … security-focused PPM … enterprise-level Agile integration … software lifecycle management … and more.
In the first three parts, we made a provocative case for adding value to the PMP by complementing it with specific packages of credentials. This one will go deep into the new product development option.
All the project measures in the world are useless if the end result is not of high quality. But how do you quantify quality? What metrics measure how good something is? Agile practices respond by making quality part of the process rather than something you measure along the way.
By following the requirement management fixes, teams can apply these few tactical steps to help improve their team’s requirements management processes.
Large scale COTS systems have spawned off multiple point-solutions within business groups. Requirements management for these satellite systems involves the resolution of a rather interesting paradox.
Integrated support for customer product planning, requirements definition, release and iteration tracking, and defect and test management.
Agile and earned value are inherently different approaches to managing projects, but they can complement each other in support of flexibility and bottom-line value. Here are three practical tips to help you bridge the gap between an agile approach and the earned value reports and measurements many organizations require.
This article will explore a different approach to gathering requirements that would not only deliver a full release, but maximize the business value as well.
In Part 1, we outlined some considerations involved in managing requirements for satellite. In this concluding part, we will look at a few specific pointers that can lead to better requirements management in such engagements.
In the previous installment, we reviewed five effective leadership behavior questions. This article provides a set of technical project management questions that assess the candidate’s knowledge of project management tools and techniques.
A recent survey focuses on the role of business analysts and requirements management in Agile IT projects.
The process of managing requirements is easy, as long as we know how to approach it. Fundamentally, the process of managing requirements boils down to three questions--which we now uncover as we bust open the secrets of the C.I.A.
Few know the evolution of Application Lifecycle Management and how the Structured Revolution of the 1970s and '80s was a major turning point in software development. This article presents a retrospective on ALM and Structured Development Life Cycles--those that shaped it, the influencing principles and the related methodologies and tools the movement spawned.
Does your organization have a “vendor management” problem — or is really a “requirements gathering and writing” problem? Here are some recommendations.
A recession doesn’t mean a project management office should slow down, much less shut down. Here are five practical activities that a PMO can embark on to keep busy and improve project management efforts in tough times.
Organizations will rely more on project management as the "need to perform trumps survival in 2010," according to a panel of senior executives and consultants.
A new global survey indicates that many outsourced projects are jeopardized by poor risk management. Pervasive challenges include a lack of foundational skills and processes, requirements gaps, and vendor delays.
Requirements management tool will complement and extend Compuware's Changepoint IT portfolio management solution.
In part three of our series, here is an overview of the key planning activities, sub-processes and deliverables involved in requirements planning, which should be driven by the business analyst as a member of the project team.
Do you have a dual personality? A PM that also has a foot in the business analyst camp has a “leg up” on the competition for jobs--and has more job security.
Many organizations understand the need to build and mature a business analysis center of excellence but are scratching their collective heads over how. Where do you start? What does it look like? Who owns it? How does it evolve? Here is some step-by-step guidance.
In conjunction with the Agile 2009 Conference in Chicago this week, our August Cool Tools roundup highlights the latest releases and updates from providers of Agile-focused solutions and services.
True stakeholder analysis involves five primary pillars of understanding. By establishing these five pillars of with all of your stakeholders, you can be certain that requirements, solutions and collaboration will be fruitful--and any dysfunction associated with your project is likely to be dissolved. Your focus will be on the solution and not ego, politics, influence or any other static garbage that prevents you and your teams from being successful.
This article highlights a few lessons learned to help future managers adjust easier to the managing requirements in an outsource model.
Here’s an overview of practical approaches and tools to actively gather requirements, involving various stakeholders--from senior executives to administrators.
A necessary step in both selecting and implementing a package is detailing the technical requirements required to run the application. Identify the hardware/software environment, interfacing systems, operational and backup procedures, and other key technical requirements.
How do expectations and desires become a project? Use these worksheets to transform objectives into concrete requirements and steps that can be accounted for throughout the project.
If you are developing an application for users, it helps to know what your basic business requirements are before you begin extensive analysis and design. This form will help you document them.
Before you launch into the nitty-gritty details of your project plan, such as scheduling and resourcing, you had better make sure the project is in alignment with business objectives. Does it fit in with the existing business and technical environments of the enterprise? Is it even feasible? Does the customer approve of the proposed solution? Have you defined the solution clearly so you can plan it efficiently? Check it against this list.
Matching people and skills to your project is tricky. Use this worksheet and checklist to help plan your resource requirements.
To formalize requirements, have one repository where you document requirements. This authoritative resource is maintained by the core team and can vary from a spreadsheet, such as this sample template, to sophisticated requirements tracking applications. Regardless of the tool used, all parties must know that there is one authoritative list and if a perceived requirement is not on the list, then it is not being addressed.
This basic Business Requirements Documentation template covers business function requirements, reports, interfaces, exceptions, and forms.
The System Requirements Specification (SRS) document describes all data, functional and behavioral requirements of the software under production or development.
How to zero in on what's important to your customers with Feature Decision Support.
What are the characteristics of a good requirement? What differentiates it from a bad one? Generally, in order for a requirement to be good, it must meet four basic criteria. Do you have what it takes?
Different stakeholder groups affected by your project will want different results. Each group's requirements will not only differ, but sometimes be in conflict. Use this template to identify conflicts/potential conflicts, gaps, contradictions or incompatibilities between stakeholder group requirements, so you can reconcile them.
Is your company about to select and implement a new information system? This sample RFP, taken from real life, was originally designed to address the current and future financial, trading and distribution operations needs of a large international company dealing with foreign countries, languages and currencies. But even if you don't have a large, international business, you'll find lots of good ideas on how to write your own killer RFP.
