Comprehensive software reviews to make better IT decisions
IIBA Shares Its Insight at Info-Tech LIVE Las Vegas
At Info-Tech’s LIVE member conference in Las Vegas last November, I had the chance to sit down with Jared Gorai and the team from the International Institute of Business Analysis (IIBA). It was a great time to catch up and see not only what the last year had brought them but more importantly what their plans and concerns are for the future. IIBA is the only association dedicated to supporting the discipline of business analysis. It offers a comprehensive body of knowledge (the BABOK® Guide) as well as practitioner support, local chapters, and certifications.
As in most organizations, the adoption of business analysis practices in Agile has been a challenging cultural change according to Jared and team, particularly since bad Agile tends to remove the business analyst or any analysis out of the sprints in favor of speed over quality.
One of the reasons for this is that every project is approached slightly differently and we’re not seeing full lifecycle tools. IIBA has addressed part of this concern with the release of the Agile Extension to the BABOK® Guide, which provides a framework to help practitioners understand the role of the BA in Agile teams rather than being prescriptive in its approach, as not all practitioners tackle the same problem in the same way.
IIBA continues to see a lack of consistency in the work that's being done and the struggles for its members who are trying to translate many techniques and best practices into shorter cycles and much smaller pieces of work. The key to resolving this has become proper requirements planning so that the same amount of work can be broken into a series of sprints that allows design development and testing forward while the BA works on future epics and stories.
Another focus for the organization is supporting senior practitioners. Organizations often focus all their effort on new and junior users and struggle to provide a value proposition to power users. Certification provides value for career advancement and mobility, but how can the organization provide support and value to individuals who have already mastered the body of knowledge? In Agile fashion, IIBA will pilot changes this year to see where it can provide value to this audience.
This mirrors a concern for many organizations as well. Organizations need to provide opportunities for mastery and growth, or they will lose their top talent. Mentoring and coaching programs allow senior practitioners to develop management skills and open up future leadership opportunities within their organization. For some practitioners, there has always been a value in being able to contribute content to IIBA, whether it’s through updates to the body of knowledge, articles, or webinars.
The final area of interest was the ongoing discussion on supporting not only techniques but also tools. With increasing speed and delivery, requirements management tools are critical to the success of your development effort and are also part of your strategic toolchain. Jared and team agreed that they are not seeing any full lifecycle tools that really address the needs of the business analyst and product owners as well as all downstream delivery activities. They continue to work with tool vendors to ensure requirements management tools align to their best practices and recommendations, which leads to an increase in adoption for the tool vendors as well. This is an example of an organization finding an extension to their value proposition that doesn't conflict with its value realization. By helping vendors in the space become more successful, IIBA is supporting the members and their continued growth.
- Organizations need to keep business analysis as part of their Agile teams. Even if you don’t have a BA, the work must be done.
- BAs need to break up their work into the smaller sprints. Develop your requirements approach with the delivery team to ensure you have the right level of detail and coverage.
- Develop a strategy for supporting your senior practitioners and helping them continue to grow.
Want to Know More?
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.
Build a Strong Foundation for Quality: Drive product satisfaction by validating and verifying quality throughout your delivery pipeline.
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.