Customer Requirements sanction start and finish of operations
Linda works with Cookware Pro Ltd, a professional cooking equipment manufacturer.
She’s working on a tender for a big chain. They want a new kind of robot. And they know exactly what they want! The stakes are high and the final delivery will be judged against their initial tender documents.
Internal work tend to dilute requirements
How is Linda going to track customer requirements down into her company’s teams and processes?
Sooner or later, she’ll end up with so many questions!
Which requirements are we covering best? Are we sure we cover them all? Have they been discussed and understood with the customer? Have we not invented expensive features that customers never asked for?
So, Linda starts a spreadsheet where each initial requirement is listed. She asks the team to document where and how requirements are taken into account.
Instead, spreadsheets or databases add to the burden
Increasingly, initial requirements generate more second-order requirements.
Updating the spreadsheet gets trickier every day. There are links everywhere. Nobody knows where and how to update. It’s very hard to get a feel of the current risk status. Poor Linda stuck with the old spreadsheet!
Next time, Linda will be using Qinaps.
See requirements through documents
With Qinaps, one can see and track customer requirements through every document. Our living documents embed and track requirements from within. There are no side databases. Therefore, as a team, everyone can see through: upstream and downstream requirements.
Import customer inputs
First, import customer initial requirements into Qinaps. Use the quick breakdown feature to represent customers’ input as a network of individual elements or blocks.
Tag initial requirements and link
Tag requirements with comments, importance, level of risk, whatever.
Connect them to one another as work progresses.
From the initial tender, you already have a first compliance and risk assessment!
See requirements through real documents
Easily check requirements captured with the customer by re-generating an identical document. All markup from requirements analysis is visible. Yet they are totally separate from the printed view. Don’t mix input and output.
As work progresses, teams go from basic design to detailed design. They document user stories and start developing features to serve them. One gets a network of upstream / downstream requirement connections. Connections allow an easy way to recognize each feature and its requirements to deliver it.
Qinaps takes care of collating childless requirements that are not yet declared as “fulfilled”. Qinaps generates input for design reviews, such as the current status of sub-requirements for each top-level requirement. Reciprocally, scope creep is chased by looking at elements with no upstream requirement.
Measure customer requirements adherence straight from your documents.
Identify key requirements and prioritize. Remove ambiguities with the customer. Flow down into further design, production, and test phases.
Subsequently, measure adherence and risks to top-level requirements. Finally, leave it to Qinaps to do the checks and alerts.
No more missed requirements. No more side tables or databases!
Image credits: Photo by Andrea Piacquadio from Pexels