Requirements Management

So much more than an eye on the schedule

5 Stages. 1 Proven Process.

Requirements management is the ongoing process of everything project related — the analysis, documentation, tracing, agreement, and prioritization of a project’s needs. The PMs handle the change control and the communication with our stakeholders. The main purpose of project management is to ensure we document, verify and meet the needs and expectations of our internal or external stakeholders as well as the end users.

As software project managers involved in requirements management, everybody must be kept happy and delighted — the end users and the client needs alike. We also prevent one set of requirements from impinging on and interfering with another. In software development, for instance, user requirements may be ignored due to the strong needs of the company. We also see to it that the right work assignment goes to the right processor, i.e. human or computer. These two can perform some processes, thus efficiency will depend on assigning them the right job.

Our Requirements Process

We are serious about requirements’ documentation. We trace the origin and each change made to every requirement. There are many requirement sources, such as other managers, middlemen, distributors, and end users. Each source has various requirements, and we trace all these to document the company’s compliance, coverage, completion, changes, and consistency in providing these requirements.
We follow a five-step process.

1. Investigation Stage

In this stage, we ask a ton of questions — about the goals, limitations, tool requirements, processes, and all other questions related to stakeholder and end user needs. During the course of any project, requirements change due to internal and external factors. These are always taken into account. At CURTIS Digital our PMs have the flexibility to cope with and address these iterative changes without compromising the main vision of every project.

2. Feasibility Stage

At this stage, we determine the requirements’ costs and the projected rate of return. These include the costs involved in the project phases, marketing expenses as well as the software and hardware costs. Basically, this is where we dive into the project schedule and budget.

3. Design Stage

Next is the design stage. As managers of requirements, CURTIS Digital PMs work closely with our User Experience (UX) design and development teams to ensure that recommended designs conform to the scope.

4. Construction & Test Stage

In this stage, we make sure that both schedule and budget are within the original scope and that the product meets the original requirements. We like to use iterative testing and prototype construction.

5. Release Stage

Not too fast … We are not done yet! Requirements management still continues even after release. We capture the product’s acceptability and user feedback. These findings inform the next generation of the product and starts the next investigation stage — beginning the cycle anew.

The cool thing is we never get dizzy!