We have explored how to define project phases and structure work across milestones. Now, the focus shifts to breaking down these phases into smaller, actionable work packages using a Work Breakdown Structure (WBS) A WBS allows project or product managers to decompose high-level phases into manageable tasks, ensuring alignment with
After defining the scope of your project, the next step is to outline the key phases that will guide its execution. These high-level phases provide a structured timeline, helping teams and stakeholders align on major milestones and expectations. While many industries have well-known standard phases, each project may require unique
“Definiteness of purpose is the starting point of all achievement” - W. Clement Stone How do you define your project? What is the first step in setting a clear direction? Addressing these uncertainties begins with creating a draft view that aligns with your objectives while identifying the areas of the
PI Planning is integral to the Scaled Agile Framework (SAFe). Typically it is a two-day event however, with new ways of remote working, PI Planning can last for more than two days. Each day follows an agenda of planned events. Ideally, it is best to have it face-to-face at a
The last event that wraps up the Scaled Agile Framework’s (SAFe) PI Planning, is the PI Planning Retrospective. Despite being the final event on the agenda, its significance cannot be understated. The goal of the Planning Retrospective is to reflect on the PI Planning process, capture feedback, and identify
Following the previous event, on the second or selected day on the PI Planning agenda in Scaled Agile Framework (SAFe), is planning Program Risks. What are Program Risks? Program risks are situations that can expose the product or projects to harm. Organizations spend a great amount of time understanding them
Kendis suggests reserving time to discuss Testing and Release strategies during the PI Planning event. Testing is a foundational and crucial aspect of software development that helps create high-quality and robust software to provide a trouble-free experience to the end user. Without it, the process of developing software is incomplete.
Planning Adjustments take place after the Draft Plan or Management Review and are usually the first event of Day 2 if you are following the two-day SAFe PI Planning. What are Planning Adjustments? Planning Adjustments are done to share any updates and communicate any high-level changes that may have been
As the dust settles after the exhilarating event of PI (Program Increment) planning, teams brace themselves for the journey ahead. PI planning marks the beginning of a new increment, filled with ambitious goals, collaborative efforts, and a shared vision. However, as the saying goes, The toughest challenges often reveal themselves
The event that concludes the first day of the PI Planning Agenda is called the Management Review. What is a Management Review? The Management Review aims to provide a platform for team leads, managers, and stakeholders to openly discuss any questions, challenges, or concerns regarding the PI Planning. The common
In the ever-evolving landscape of Agile methodologies, the Scaled Agile Framework (SAFe) has recently made a significant terminology shift by rebranding Scrum Masters as "coaches." While this change signifies a broader scope of responsibilities and a more holistic approach to leadership, it also prompts a critical reflection on
The event that shows the results and summarizes the collective efforts of all the teams involved in the Team Break-Out sessions in the PI Planning Agenda, is called the Draft Plan Review. What is a Draft Plan Review? The Draft Plan Review is where teams give short presentations on their
PI Planning
As we approach halfway towards the first day of the PI Planning Agenda, after setting the Business Context,Product and Solution Vision, and Architectural Vision, the next recommended event that follows is the Planning Context. What is Planning Context? The Planning Context is when the planning processes and expected outcomes,
PI Planning
After establishing solid ground for PI Planning in the Scaled Agile Framework in the PI Planning Agenda with the Business Context and the Product and Solution Vision, the third recommended event that follows is the Architectural Vision. What is Architectural Vision? The Architectural Vision focuses on the technical aspects of
PI Planning
After the Business Context is presented and has provided the basis for PI Planning in the Scaled Agile Framework in the PI Planning Agenda, the Product and Solution Vision is the second event that follows. What is Product and Solution Vision? The Product and Solution Vision aims to highlight the
PI Planning
The PI Planning event in the Scaled Agile Framework (SAFe) goes for 2 or 3 days. The PI Planning agenda consists of various activities that aim to cover a vast scope of the Program Increment. The first event that takes place and sets the tone of the entire PI Planning
Scaled Agile
Epics, Features, and User Stories are trending words in the Agile community. Any organization that has adopted the agile way of working is seemingly obsessed with epics, features, and user stories and these organizations cannot seem to get enough of them. Indeed these work items are a critical part of
Scaled Agile
Product Management is a core and indispensable element of Agile Development in any Scaling Framework. It needs to ensure the creation of products or solutions to completely meet the needs of the end users. In order for this to be successful, a tremendous amount of work and individuals are required
Scaled Agile
Have you ever had to face problems where you have considered an epic in Jira as a portfolio or a program epic, and you are unsure of the difference between a portfolio epic and a program epic? Do you find it difficult to plan and track your version of a
Objectives and Key Results
Objectives in the Scaled Agile Framework (SAFe) play a critical role in aligning the efforts and focus toward achieving the goals set by the organization with their primary benefit being; becoming the basis for tracking the progress of the Program Increment in SAFe. Tracking of the objectives becomes easier with
Events
“For me, the highlight of the event has been the collaboration and the connecting with the people… I’ve seen a lot of innovative ideas coming out.” - Andrea Grant, CEO of Framework Projects We at Kendis loved seeing both new and familiar faces at the 2023 SAFe Summit in
PI Planning
Kendis provides many great capabilities to make your remote PI Planning experience super easy and engaging. Once you finish your Quarterly/PI Planning, the next step is to find ways to make your PI Tracking as automated as possible. In your own Agile tools, Jira or Azure DevOps tracking is
In Kendis, Sprint Tracking (or iteration tracking) is much more than just tracking story points and producing burndown and burnup charts. At Kendis, we provide a range of features that will expand your sprint tracking capabilities, all while staying integrated with your ALM tool. Let's dive in to
When it comes to executing your Program Increment (PI) and as discussed in our previous article, a significant amount of time is dedicated to tracking. Alongside, upcoming PIs are also being scheduled and planned that involve an echelon of factors related to product breakdown and many technical, financial, and social