1. Boutique product development company
It is amazing what you can accomplish when you have a client-centric team to deliver outstanding products.
2. Boutique product development company
It is amazing what you can accomplish when you have a client-centric team to deliver outstanding products.
Requirements
Management
Mujtaba Pracha | Project Manager
3. Tips for better Requirements Management
What will this achieve?
• Save Time
• Avoid Project Failures
• Share Requirements
• Delight your Customers
• Impress your Executives
4. Tip 1: Capture 100% Requirements
• Requirements come from all directions. From customers, prospective customers,
Sales, Business Development, Executives
• They come to you in all formats. Emails, Meetings, Conference calls, Hallway
chats, Instant messages, Word documents, Excel spreadsheets.
• Capturing 100% of these requirements is a huge challenge!
How to achieve this?
• Use a tool like base camp to diligently capture all requirement statements. Use
either a single thread for this purpose or a To do list
• Create a template using Excel or similar spreadsheet software.
• Educate everyone in your team of this process
5. Tip 2: Verify Requirements
• Requirements often tend to be vague, ambiguous and sometimes even self-
conflicting!
How to achieve this?
• Verify immediately (within a day or two) following the receipt of the requirement
people often tend to forget the reason for and details of the requirements they
asked for!
• Make it easy for the source of the requirement to provide further details and
clarifications. Use base campredmineJIRA diligently to consolidate all such
discussions
• Team culture where all involve question requirements rather than accepting them
6. Tip 3: Completeness Of Requirements
• Incomplete requirements lead to project delays, unmet customer needs, lost
deals,
and ultimately product failure. As a result, it is critical to ensure completeness of
your requirements.
How to achieve this?
• Describe business needs and use cases underlying the requirement
• Include functional as well as non-functional parts of the requirement.
7. Tip 4: Prioritize Requirements
• Prioritizing requirements benefits everyone – those who create it as well as those
who consume it . And of course, it ensures that you spend resources in the right
areas.
• In assigning priority for each requirement, we should take into account factors
such
as competitive differentiation, market trends, company strategy, and the needs of
key customers.
How to achieve this?
• Keep prioritization simple and systematic. For example, use a scale of:
• High, Medium, and Low
• P1, P2, and P3
• High/P1 could mean "Must Have", Medium/P2 could mean “Important", and
Low/P3 could mean "Nice to Have, but Not Essential".
• Add a column for "Priority" in your template and ensure that it always gets
completed.
8. Tip 5: Communicate Across Teams in Real-Time
• Communicating requirements in a timely fashion (as close to real-time as
possible)
across all teams – product management, design, engineering, QA, etc – is
essential to ensure that the requirements are accurate, complete and properly
understood by everyone.
How to achieve this?
• Establish clearly defined communication process for requirements and ensure
that everyone understands the process.
• Educate everyone on the importance of communicating requirements in a
timely fashion.
• Make use of tools such as wikis, ticket management tools(Redmine) and
discussion boards – in addition to emails and meetings. These tools capture
communications in a central archive..
9. Tip 6: Trace Dependencies
• One area where a lot of teams can improve their requirements management
process is in tracing dependencies between requirements
• Documenting dependencies between requirements (i.e. "tracing dependencies").
will enable team to do simple impact analysis
How to achieve this?
• Create a template that includes "Dependencies" field and ensure that it is
completed carefully.
• When writing requirements documents, clearly map out key dependencies.
• When deciding to omit a requirement from a project during the middle of the
project, make sure to perform a dependency analysis.
10. Tip 7: Track All Changes to a Requirement
• Challenges due to Agile model- Requirements change throughout the project
• Tracking changes to each requirement and who made those changes allows your
team to understand how a requirement evolved, perform root cause analysis, and
alleviate personnel issues in a project team related to these changes
How to achieve this?
• Use project wiki’s or base camp to do this instead of Excel sheets only
• Try to implement 4-5 out of the 7 mentioned and you will see an improvement in
overall project communication and relationship with client
