Traditional project management practices do not disappear as an organization transitions to Agile and product-centric delivery. These capabilities are often distributed to other delivery roles, such as resourcing for team leads and financing for product owners, if organizations decide to gradually dissolve the project manager role. See our Build a Better Product Owner blueprint for more information on how product owners are assuming project management responsibilities. Teams leverage application lifecycle management tools to manage and govern their delivery work, but they do not offer the resource planning, time tracking, financial management, and other project management capabilities that are needed for successful delivery.
Atlassian’s Jira remains a popular collaboration tool for teams looking to better coordinate work. However, it requires third-party add-ons and integrations to support end-to-end artifact traceability and product delivery. Tempo fills Jira’s project management capability gap by enabling managers to:
This plug-in enables real-time updates of key dashboards whenever work progresses through the delivery pipeline in Jira and can motivate bringing project management and delivery tools closer together because of a common toolset. Teams can easily integrate Tempo into their workflow given that Tempo leverages the Jira UI. Tempo does not provide the more advanced or comprehensive project management capabilities (e.g. forecasting) that traditional project management tools provide.
Unfortunately, this tool can reinforce project management practices, which risks the delay or resistance to fully transition to a product-centric model. Sufficient training and onboarding are needed to ensure project management capabilities complement product-centric practices.
Tempo enhances the value of an organization’s Jira investment by generating the project dashboards and reports stakeholders and management ask in real time. This plug-in does not provide the comprehensive capabilities as other project management tools but it can be just enough to satisfy stakeholder and management concerns. Much like any other integration, this plug-in should motivate the evaluation of the application lifecycle management architecture, particularly the integration of your tools and the relationship among all of your artifacts, in order to make the most value of your tools.
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.
Google has announced several updates to its G-Suite offering, which aims to heavily integrate and better secure its teamwork applications. The move represents a clear attempt by Google to directly compete with Microsoft’s office productivity suite, with several of the G-Suite updates mirroring the logical architecture of Office 365.
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.
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.
Aha! introduces scenario planning to give product owners the ability to create and compare multiple release approaches based on team capacity and backlog priority.