Comprehensive software reviews to make better IT decisions
Agile Doesn’t Mean No Requirements
We had a chance to talk with Ashu Potnis, vice president, and the TechnoSolutions TopTeam Analyst team at their booth at the 2019 Project World/Business Analyst World conference in Toronto about what trends they were seeing in the industry. TechnoSolutions provides requirements management solutions that integration with HP Quality Center (now Micro Focus Quality Center) and Microsoft Visual Studio.
Not surprisingly, TechnoSolutions continues to see organizations struggling with requirements analysis and management in their Scrum teams. Many IT teams moving to Agile focus exclusively on user stories and light acceptance criteria as their requirements and use delivery management tools like Jira and Microsoft Team Foundation (now Azure DevOps Server). Although these teams were happy with the transition to Scrum, they struggled to deliver end-user value and saw a significant increase in defects.
This is consistent with Info-Tech’s research and member advisory experience. When many organizations begin Agile, they start by doing Agile before being Agile. Project management of key milestones and compliance items, as well as business analysis and requirements management, are still critical to delivering value in an Agile environment. The Agile manifesto does not state “no documentation,” but rather it challenges teams to find the appropriate level of documentation and not create documents just for the sake of a document.
Info-Tech’s blueprint Implement Agile Practices That Work to develop an iterative approach to rolling out
Agile within your organization.
TechnoSolutions is now seeing a reversal of this trend, just as Info-Tech is helping members reach the next level of Agile and requirements maturity. Organizations are focusing more attention on analysis and requirements management in a dedicated requirements management platform, like TopTeam Analyst, and using tool chain integration to track stories in their delivery management platform. By creating a reusable library of current state requirements, organizations are able to improve their impact assessments, story sizing, and defects due to missed requirements and constraints.
- Managing requirements as an asset is even more important in Agile methodologies and DevOps. Teams don’t have time to rediscover current state, dependencies, and constraints in each sprint.
- Find the right level of documentation to support the entire product lifecycle.
- Start with your people and processes and then build a tool chain that supports your teams and processes. Favor integration between tools over individual tool features.
- Remember, a person with two watches never knows what time it is. Define a system of record for each type of information, update it in one location, and share information between systems so that teams have it when and where they need it.
Want to Know More?
Looking to improve your requirements management and Agile maturity? Download the following blueprints:
- Build a Strong Approach to Business Requirements Gathering
Poor requirements are the number one reason that projects fail. Take a strategic approach to optimizing requirements gathering in order to give the business what it needs.
- Implement Agile Practices That Work
Improve collaboration and transparency with the business to minimize project failure.
Traditional accounting practices are tailor made for waterfall project management. Organizations that have transitioned to the use of standing product teams using Agile and DevOps need to transform their accounting practices as well or they will leave valuable capital expenditure dollars on the table.
IBM is changing the terms of its ubiquitous Passport Advantage agreement to remove entitled discounts on over 5,000 on-premises software products, resulting in an immediate price increase for IBM Software & Support (S&S) across its vast customer landscape.
So you’ve gone Agile. You do daily scrums, retrospectives, and all the “right” Agile ceremonies. But still your organization isn’t quite convinced. It is now critical to balance the drivers and goals of both Agile and traditional thinking in order to achieve organizational success.
Do you feel like your Agile teams are treading water – going through the motions but never going anywhere? It’s a risk, and practices such as daily standups, retrospectives, and demonstrations need to be used wisely or you risk losing discipline to meeting fatigue.
Stakeholders expect the speed and responsiveness of product delivery does not come at the expense of quality. QA tools offer retailers the ability to continuously ensure both business and technical quality standards are upheld, but these tools should not be viewed as a silver bullet.
When trying to implement Agile as a defined process, Scrum turned BAs or other roles into order takers with the title “product owner.” This undermines the entire value proposition of product management.
No matter how good your product roadmap and backlog are, they are only as good as your audience’s ability to understand your vision and priority.
The scrum master is like the conductor of an orchestra, ensuring that every piece fits together at the right time to create something greater than the sum of the parts. You don’t have to know how to play each instrument, but you do have to understand what each part contributes to the overall masterpiece.
Tools are important to product teams, but only when they support solid people and processes.