Comprehensive software reviews to make better IT decisions
Draw.io Extends Confluence for Design
One of the major limitations of collaboration and discussion tools is the limits on the type of information that can be shared. Text and static images help, but to have deeper conversations, teams may want to extend their platform to include diagraming and design tools. Teams are one step closer to a comprehensive collaboration platform with the addition of draw.io to the Confluence platform.
In the article “A Side of Diagramming With That Burger? The Top Ten Atlassian Third Party Apps” published on March 29, 2019, Confluence (42%) and Jira (58%) are the two top apps in the Atlassian marketplace. Draw.io Diagrams for Confluence is the top diagraming app with 5% growth and the highest paid user count (23,6551). According to the assessment, teams using Confluence draw.io may be a viable alternative to Microsoft PowerPoint and Visio by adding deeper collaboration to team drawings.
Image source for draw.io example: Atlassian Marketplace
- Collaboration requires more than text or discussions. Information needs to be communicated in formats that create a common working understanding.
- Extending your collaboration platform to include design and diagraming tools will improve the quality of team interactions and understanding.
- Ensure that the assets you are developing apply throughout the product delivery lifecycle. Your tool chain needs to support your people and processes, not the other way around.
Want to Know More?
Developing assets through collaboration platforms still needs to be part of your requirements management and quality programs.
- 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.
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.
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.