Comprehensive software reviews to make better IT decisions
ALM Works Extends Its Structure.Gantt Capabilities
ALM Works’ Structure is a Jira plugin that enhances and expands Jira’s capabilities for project management, requirements management, QA, and help desk. Structure enables enterprise-level organization of Jira issues and stories with multi-level, cross-team, and cross-project hierarchies. This application is available in the Atlassian Marketplace.
- Work breakdown structure, which defines the scope of work and is built using Structure functionality.
- The chart itself, which visualizes tasks on a timescale, showing start and finish dates, dependencies between them, and other management information.
Unlike other project management tools, the Structure.Gantt integration with Jira provides accurate and up-to-date information of delivery work progress as it happens and enables managers to tap into the underutilized data contained within Jira and Structure.
- Structure.Gantt becomes a paid app (2.0)
- Resource Leveling allows users to automatically resolve overallocations for a single resource or group of resources (2.0)
- Visualization of delivery progress against defined baselines (2.0)
- Specify duration separate of work for auto-scheduled tasks (2.1)
- Indicator when a task is not visible on the chart due to insufficient permissions or the Gantt configuration, along with an explanation (2.1)
ALM Works’ Structure.Gantt provides versatile Gantt chart features as a tool to better manage programs and portfolios, a noticeable missing feature in Jira. Organizations that are already invested in Jira and will be managing large programs involving multiple teams will see significant value with Structure.Gantt’s low-cost extension. Atlassian’s Portfolio for Jira attempts to address their portfolio management gap, but its value is yet to be seen.
Want to Know More?
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.
If an image is worth a thousand words, a visual roadmap will save you a thousand hours.
The application portfolio management (APM) tool space can be a confusing one, as many software vendors offer their own take of what APM is. Enterprise architecture, application management and project portfolio management tools offer an APM use case, but these are often quite skewed the primary function of the tool.