Discussions
-
Tactical way to handle PI Confidence Vote!
Scaled Agile Framework (SAFe) came up with the concept of a PI confidence vote as an activity towards the end of Day 2 of the Program Increment(PI) planning event. PI confidence vote is an activity where everyone raises their fists up and votes on a scale of 1 to 5, where 1 being the lowest and 5 being the highest. As an…
-
Understanding the Dependency Workflow in Jira Align
Although this topic has been discussed on multiple platforms, just adding to the collection of dependency management. The image shows the dependency workflow in Jira Align. A dependency is a contract between two teams: the requesting team creates it, and the responding team either accepts it or proposes changes, which…
-
Story points and estimation
To use story points effectively in Jira, involve the entire development team in sprint planning using relative estimation techniques like Planning Poker. Assign points based on complexity, effort, and risk, using a consistent scale and avoiding tasks that exceed a specific size. Use Jira to track velocity, discuss…
-
Dependency Management Use Cases in Jira Align
Dependency management in Jira Align handles a couple of scenarios which are listed below. Dependency between Teams within an ART(Agile Release Train)/Program * Teams from different ART(Agile Release Train)/Program Scrum Team depending on Kanban Team within/different ARTs Kanban Team depending on Scrum Team within/different…
-
Understanding Capacity Planning in Jira Align
The capacity page is designed to help you develop a comprehensive plan that clarifies how much work your teams can achieve during a program increment (PI). It offers a user-friendly, flexible, and spreadsheet-like interface that allows all managers to easily view and contribute. Based on user inputs, the page calculates…
-
Lean Portfolio Operations and Governance Activities
Recommended checklists based on the initial configuration of the Lean Portfolio level operations and governance activities outlined I&A Workshop (Quarterly) Step Short Description Jira Align Page Demo Features Demo the features that have been accepted as part of the PI. ART Board Objectives Check-In Review each objective…
-
Timeline for preparation of PI Planning at the Portfolio Management Level
The Pre-requisites Preparation for the upcoming Program Increment (PI) Planning at the Portfolio Management level is a process that initiates with the execution of the current PI at the team level. This crucial phase begins during the first and second sprints, where the Portfolio Management team, tasked with overseeing…
-
Jira Align and Azure DevOps Integration: Best Practices
Before integrating Azure DevOps with Jira Align, there are some best practices that should be considered. Some are a little more rigid than others; while others can lend themselves to some workarounds. Let's explore further to understand what these are, why these are important and the potential impacts. Projects Support…
-
Grouping Cross ART releases in Jira Align
The fix versions in Jira are specific to a Jira project. However, the intent to create, plan, and visualize a Go-Live Release runs across multiple Jira projects. Jira Epics and stories built across multiple Program(s)/Agile Release Train(s) in different Program Increment/Quarters need to be clubbed to form Major/Minor…
-
Jira Align Solution Layer ( Capabilities ) to have or NOT to have is the Question?
For organizations where the products and/or services are so complex that an Agile Release Train is not sufficient, the intent is to have a Solution Train. This is applicable for organizations in which multiple Agile Release Trains work together on one or more complex services and/or products. Typically, the solution train…
-
Does Jira Align support waterfall-type of development/portfolios, along with Agile?
Agile has become a widely recognized term, yet it's important to acknowledge that it doesn't suit every organization perfectly. Many companies globally have successfully implemented Agile methodologies in certain areas of their operations, while other segments continue with traditional practices. This is not always by…
-
Custom Hierarchies and Custom Rooms
An organization might have a need to classify work at the “Team of Teams” level by Product. While the Product module in Jira Align allows for a single product selection on a feature(work item as a group of stories), an organization might require features completed to apply to multiple products. In this scenario, Jira…
-
Quarterly Business Review(QBR) with Jira Align
Quarterly Business Review(some basics first) What: Integrated Demo of features delivered over the course of Quarter/PI When: End of PI, different than regular system or sprint demo/review How: It’s presented with working software, not PowerPoint Who: Business leaders, Portfolio managers, Epic owners ( of course ART) Key…
-
Bringing Agility to Traditional Portfolio/Project Management
What does an organization following a Traditional Project Management do differently than an organization following an Agile framework? The main difference is that Traditional Project Management is a linear system of working that requires the team to complete each project stage before moving on to the next one while Agile…
-
Why Innovation and Planning Sprint?
Scaled Agile Framework(SAFe) states about the Innovation & Planning(I&P) Sprint, which is the last sprint of PI. Many organizations don't see the value of having one and see that as free time for the Agile Release Train(ART), while others consider this as a buffer sprint. Yes practically, for important commitments that…