Comprehensive software reviews to make better IT decisions
Atlassian Embraces Continually Changing Plans With Portfolio for Jira Server and Data Center 3.0
Portfolio for Jira Server and Data Center 3.0 (called “Portfolio 3.0”) provides improved capabilities enabling easier modification, communication, and collaboration on team roadmaps.
Atlassian accomplishes this via three key changes:
- Greater visualization of plans
- Set a plan that reflects organizational reality
- Ability to respond to change quickly and effectively
According to Atlassian, Portfolio 3.0 enables users to better surface and understand cross-project and cross-team dependencies through a clearer visualization at any level of hierarchy (from initiative down to user story).
Additionally, changes to your plan can quickly be evaluated through leveraging of scenarios (or sandboxes according to Atlassian) to see best- and worst-case options. Nothing is committed until it is reviewed and adjustments are completed. As new items get added to the backlog, roadmap plans will be automatically re-generated for evaluation and commitment.
As plans change, new dependencies and issues may emerge. Portfolio 3.0’s new interface surfaces these items quickly and effectively, thereby allowing the team to take action to ensure value is delivered to stakeholders on schedule.
Successful delivery is not just a problem for the project manager. Business, IT, and Operations continue to align closer together than ever. This requires all team members to have a shared understanding of requirements, outcomes, and timing of deliverables.
Atlassian enables teams to effectively respond to business changes that impact requirements and scope. Those impacts can be surfaced in an actionable, easy-to-understand way that enables greater collaboration on requirements and improved delivery outcomes.
Source: Atlassian at SoftwareReviews, Accessed September 27, 2019
Want to Know More?
Tools are only valuable when the contributing practices and processes are robust. We suggest the following research:
Build a Better Backlog – A well-built backlog helps facilitate effective product planning and delivery.
Build a Product Roadmap – A roadmap is only effective when it can be communicated to the organization.
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.
Is it true that everything that can go wrong will go wrong? Don’t bet on it to not.
While Microsoft is not a prominent player in the RPA space now with its Power Automate solution, compared to Blue Prism, UiPath, and Automate Anywhere, its latest acquisition of Softomotive, maker of WinAutomation, demonstrates Microsoft’s dedication to mature and expand its RPA offerings.
Test data management tools offer you the ability to provision, mask, and govern the access and use of your test data, alleviating these manual, laborious and error-prone tasks from your testing, operations, and DBA teams.
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.
Agile systems delivery (implemented through Scrum) is quickly becoming an accepted norm in IT. But using Scrum successfully in an organization requires a deep understanding of how it works and why. For example, many of our members don’t understand the importance of selecting a Product Owner who has three ears.
Reeling from the pandemic response executed by governments all the over world, companies are accelerating their implementation of low-cost automation. That bodes well for UiPath – a leader in RPA aiming to go public this year.
Thor, the Norse God of Thunder, tells Jane Foster, the woman he’s trying to impress, that on his home world of Asgard, the realm eternal, science and magic are two sides of the same coin. Had Jane been a part of the operations teams at Google (or other mature online service providers), she would have immediately realized we have a similar technology right here on good old Earth. We call the science site reliability engineering (SRE), and service level objectives (SLO) is the magic behind it. SRE is a powerful concept for organizations that are serious about keeping their customers happy. It is therefore important for them to develop well-thought-out SLOs and make certain that management is intellectually equipped to derive valuable business perspectives from them.
Hell hath no fury like a customer not being able to access an online service when they want to. They expect the online services to always be on, always be accessible, and always treat them like there’s no one else in the world who matters more. Thank heavens then for giving these online services the ability to use site reliability engineering (SRE) to keep their customers happy, engaged, and most importantly, feeling valued.