The Enterprise, Solution, and System Architects indeed have a critical role in executing the Program Increment (PI). Learn SAFe Best Practices of how all three roles work together as well as working with Product Management, Stakeholders, and Agile Teams.
Enterprise, Solution and System Architects must:
a. Portfolio: Strategic Themes are crafted into Portfolio Vision, and Business and Technical Epics are prioritized and mapped out into a long-term Road Map. This forms the basis and essential input for Program Increment Planning. Learn to write Epic Enablers, Capabilities, Features, Stories, and score them with WSJF.
b. Capacity Planning and Runway: Solution and Systems architects work with different levels of Product Management and suppliers to prioritize at the Solution, Release, and Team level. Be sure your PI plan has the right mix of Business features and Technical enablers.
c. Build Around Value: Architects work closely with the business to identify delays in the delivery of Value and create Agile teams to address. Learn to the art of Value Stream Mapping and ART Formation.
d. PI Planning: Architects work across teams and trains to elaborate on how the Architectural Runway will come together and work out ‘Hot Spots.’ Learn how to create the Solution, ART, and Team leave the PI board and map the dependencies.
e. Post PI Planning the Architectural Runway is modified/strengthened to adapt to the surprises found during PI Planning.
f. During PI execution; Architects participate in several Team, Train, and Solution level ceremonies, including Arch, PO Sync, Scrum of Scrums, Demos, and Retrospectives. Learn how architects keep the ART momentum (Velocity) going.
g. Best Practices for Architects in LEAN center of Excellence, Community of Practice, and Guiding Coalition. It is becoming a key leader for both business and technology.