Learn about techniques to use when adding to a process, product, or system, and how the uniqueness of enhancements work with requirements brings a potentially different approach.
- Most backlog items and requests that BAs work on are about adding to or modifying a solution. When adding to, enhancing, or fixing an existing solution, it's easy to put your blinders on and just manage each request individually, but this is actually a bit of a trap. Many teams have a backlog of enhancements, defects, and requests associated with existing solutions. The trick is figuring out which of these many items are important and actually worth doing.
It's not an exaggeration to say that over half of an average team's backlog items should never get done. So much of it is multiple requests for the same root cause, or just not as important as spending time creating the future and innovating. How do we ensure that what we're working on is the right stuff? It's important to analyze the backlog to identify patterns. We analyze this by asking questions, such as: and also and lastly It's also important to connect with the requester.
Use elicitation techniques to understand why it's important for the item to be completed. Explore alternatives for how the request could be solved. Many of these additions to solutions can start out the same way as a new system, using context to elicit and analyze where the change is impacting existing parts of a solution. Also, before implementing an enhancement, You never know what patterns or hidden connections you might find.
The biggest mistake I see is simply taking each request at face value and quickly implementing whatever is asked for. This tends to create a lot of rework and layers of defects, rarely actually fixing the problem that created the request to begin with. Adding to the solution can be great for the user, but also can be something they wish they never asked for. Great analysis will cut through this and make sure the right work gets done.
LinkedIn Learning (Lynda.com) is a PMI Registered Education Provider. This course qualifies for professional development units (PDUs). To view the activity and PDU details for this course, click here.
The PMI Registered Education Provider logo is a registered mark of the Project Management Institute, Inc.
- What's elicitation and analysis?
- The relationship of elicitation to analysis
- Elicitation techniques
- Using interviews, brainstorming, and experiments to elicit requirements
- Analysis techniques
- Working with process models, context diagrams, and decision tables
- Adding to a process, product, or system