Comprehensive software reviews to make better IT decisions
Merging Aha! Product Management With Microsoft Teams Delivery
One of the ongoing challenges in software delivery continues to be managing information across multiple systems of record in the delivery tool chain. With different tools providing compelling value to teams throughout the delivery process, there isn’t one tool that meets everyone’s needs. The next best approach continues to be integration with designated systems of record.
Aha! made another significant step to become integrated into the delivery value chain. Aha! is a collaboration toolset that allows product owners to gather and manage inputs from different sources (e.g. customers, technical teams, market research, support) into cohesive roadmaps and feature backlogs. The platform allows teams to propose enhancements and manage the discussion.
Aha! recently announced in a blog post an additional integration with Microsoft Teams as a way to extend these discussions and feature implementations into delivery teams already using Microsoft Teams. Aha! integration is customizable so that you can control how information and discussions are added to Teams without overwhelming users with excessive topics and notifications. Aha! also built in delays to allow discussions to mature before sending to Teams, again helping to reduce notifications and distractions from other discussions and updates.
Aha!’s inclusion of Teams support adds to its existing integrations, which include common tools such as Jira, Azure DevOps, Salesforce, GitHub, Slack, and Okta. This gives your team options on how to leverage other integrations as well. Development teams using Microsoft tools can extend Teams into Azure DevOps Server (previously Foundation Server), SharePoint, and other products.
- When defining the flow of information through your delivery chain, define the people, processes, and information first. Then find the tools that best support your activities and provide integrations to facilitate the flow of information.
- Always start with a pilot project to make sure the tool and interface work well for your team’s needs.
- Plan your information management and flow ahead of time to reduce conflicts and rework later.
Want to Know More?
To ensure that your people, processes, and culture are ready for the product delivery tool chain, follow our guidance in the following blueprints.
Implement Agile Practices That Work: Improve collaboration and transparency with the business to minimize project failure.
Transition to Product Delivery: Stop delivering projects. Start delivering products.
Implement DevOps Practices That Work: Streamline business value delivery through the strategic adoption of DevOps practices.
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.