fbpx

Architectural Vision in PI Planning for SAFe

Architectural Vision in PI Planning for SAFe

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.

Contents

What is Architectural Vision?
How is the Architectural Vision Presented?
How to Prepare for the Architectural Vision in 16 Steps
Kendis Tips for Presenting the Architectural Vision

What is Architectural Vision?

The Architectural Vision focuses on the technical aspects of the development in the Program Increment (PI) and how they relate to the business and other key areas while working towards the objective of what needs to be done in the PI and how it will be done. The System Architect generally leads this discussion by talking about the non-functional requirements (NFR), enablers, systems, components, enhancements, and improvements to the features relevant to the PI and how they will provide value to the end user.

How is the Architectural Vision Presented?

The duration of the Architectural Vision is usually one and a half hours where a slide deck can be used to present the points of the discussion. Diagrams or flow charts can also be used to represent the overall state and the end goal of the system.

To obtain a better understanding of the product and to ensure smooth developmental work, applicable risk, and security control requirements or validation should also be addressed and considered before presenting the Architectural Vision. For example, it is important to engage with the compliance department to know the rules and regulations so that the work remains within what is defined. Speaking with the teams and component owners to get their feedback helps in relating all the efforts towards the development work.

It is beneficial to utilize the Product and Solution Vision as it provides a runway for new features or functionality to be added so that all the work that is done relates perfectly to the product.

How to Prepare for the Architectural Vision in 16 Steps?

Below you will find Kendis’s list of recommended activities to help prepare for presenting the Architectural Vision.

  1. Prepare a slide deck
  2. Have an abstract view of what is going to be presented
  3. Find out how the products are categorized and speak about those products
  4. Prepare workflow and diagrams concerning those categorized products
  5. Define the necessary risks and security controls
  6. Incorporate the work that needs to be done in the PI within enablers, stand-alone features, product features, or epics.
  7. Speak to the teams involved and refine the vision so that the right information is presented
  8. Highlight known dependencies between teams or external parties
  9. Kendis recommends discussing branching strategies and dependencies in developmental environments
  10. Try to avoid having a long list of features to discuss. If you do have a long list of features, categorize features within the product or architectural framework
  11. Manage time to discuss features that have more complexity. If there is anything new to discuss regarding the design, components, or architectural framework, if possible have these discussions with the relevant teams prior to the PI Planning.
  12. Decide the order for the unprioritized features with the teams along with the product manager
  13. Identify the objectives or goals that need to be achieved in the upcoming increment or quarter
  14. Know the complete scope of the milestones
  15. If there are features that are relevant to the milestones, make sure they are highlighted. Prioritize the features that are going to be part of the milestone.
  16. Closely collaborate with all the product managers and any other areas impacted

Tips on preparing for the Architectural Vision in PI Planning in the Scaled Agile Framework

Kendis Tips for Presenting the Architectural Vision

Once you have prepared for the Architectural Vision, you can ensure an effective presentation on the day itself.

  • Make sure that you’re audible, as the content you are showing will set the architectural context of the PI
  • Provide a brief introduction about yourself
  • Present your slides
  • If you have external parties and vendors, general improvements, or transformation of the design, it should be highlighted and discussed
  • If your designs relate to categorized products provided by the product management, briefly talk about the as-is technical designs and discuss the enhancements that need to be made. Take any questions related to the enhancements
  • Remember to talk about what is specific to this PI Planning and move to the subsequent categorized products
  • Discuss risk and security controls if applicable
  • Show a categorized list of features that would keep everyone engaged and be prepared to go into detail
  • Talk about the goals or milestones that need to be achieved for the product
  • Speak with confidence and be positive remembering the people are here to reach the goals that you set
  • Prepare time for questions and answers
  • Make sure to keep to the suggested time so it does not affect or delay the time for future activities that are part of the PI Planning agenda

How to present the Architectural Vision during PI Planning in the Scaled Agile Framework

The Architectural Vision is necessary for establishing a plan for achieving technical excellence. Importance should be based on the “HOW” we are going to achieve the set business goals from the organization and make the necessary architectural enhancements. The Architectural Vision acts as an enabler for the product in the PI Planning to be implemented and enhanced. Whenever the opportunity comes through events like PI Planning, System Demos, team sync-ups, and various discussions the architectural vision should be reviewed and discussed to ensure that all the efforts are towards a technical direction and feeds the requirements of the long-term roadmap of the architectural vision.

To learn more about Kendis, click here.

 

Explore Articles about Scaling Agile

Pick your next read from our vast library of specialized content. These Kendis articles help the Agile transformation leaders develop a deeper understanding and provide fact-based insights that contribute to decision making on critical scaling issues.


Got Questions?

Talk to our product expert to understand how Kendis can help your organization in your scaling agile journey.
Contact us now Get a personalized demo for free.



Play

Watch Video
Program reports and analytics

Program reports and analytics

Collaborate for the completion of a Release Train with a wholesome overview of all activities on your Program Board summarized into graphical and tabular formats.

Dependencies Management

Dependencies Management

Summarize all your PI dependencies into one meaningful and simple dynamic solution that automates dependency status updates throughout the PI according to the triggers you select.

Risk Register Tracking

Risk Register Tracking

Address and visualise the present and upcoming risks of your Program Increment, sprint or iteration to swiftly identify and smoothly mitigate them.

Feature Tracking

Feature Tracking

Visualise features progress, development, addition and removal, across sprints and teams in a simple and easy manner.

Scope Change Tracking

Scope Change Tracking

Track your PI’s scope and other changes post-planning, saving yourself hours of manual work and eliminating the possibility of human error.

Collaboration, communication and transparency lie at the heart of Kendis. It brilliantly reduces all the painful efforts and makes the entire process of planning your Program Increment a very easy task.
PI Objectives Tracking
Play

Watch Video

Dependencies are essential in recognizing, identifying and correctly mapping factors that are affecting your progress. In Kendis you can create multiple dependencies across your Program board and track them.
Dependencies Management
Play

Watch Video

With Kendis you can transparently address and visualize the present and upcoming risks of your Program Increment, sprint or iteration in a way that makes it painless to identify and analyze.
Risk Register Tracking
Play

Watch Video

Create objectives for each team or for your Program and link those with any item present your board. This allows you to choose precisely what features and stories are contributing to the objective.
Feature Tracking
Play

Watch Video

An extremely vital and powerful feature that gives an overview of all the recent activities that are being done. Presented in graphical or tabulated formats, you obtain all the necessary information in just a glance.
Scope Change Tracking
Play

Watch Video