What is PSI in Scaled Agile Framework?
It is wonderful that the whole Scaled Agile Framework can be distilled down to one compelling graphic. The PSI, of course, is the "Potentially Shippable Increment" at the heart of the program layer of SAFe. Similarly, what is a potentially shippable product?
What is a PSI in safe?
The PSI, of course, is the "Potentially Shippable Increment" at the heart of the program layer of SAFe. Similarly, what is a potentially shippable product?
What does PSI stand for?
PSI stands for Potentially Shippable Increment (Agile Software Development) Suggest new definition. This definition appears frequently and is found in the following Acronym Finder categories: Information technology (IT) and computers.
What is Pi planning in agile?
Program Increment (PI) Planning is a cadence-based, face-to-face event that serves as the heartbeat of the Agile Release Train (ART), aligning all the teams on the ART to a shared mission and Vision. PI planning is essential to SAFe: If you are not doing it, you are not doing SAFe.
What does PSI stand for in agile?
Increment or Potentially Shippable Product An Increment (sometimes referred to as a 'Potentially Shippable Product') is the value delivered for the customer via the Product Backlog Items completed during a Sprint.
How many sprints are in a pi?
5 SprintsTeams apply common iteration lengths – within a PI there are 5 Sprints of 2 weeks each and each team adheres to the iteration length.
What is a potentially shippable product?
Potentially shippable is a statement about the quality of the software and not about the value or the marketability of the software.” When a product is potentially shippable then that means “that all the work that needs to be done for the currently implemented features has been done and technically the product can be ...
What does PSPI stands for in agile?
In Scrum, the goal is to have a Potentially Shippable Product Increment (PSPI) at the end of every sprint. However, many teams fail to accomplish this on a regular basis. I believe achieving this is what unlocks much of the power of agile.
Who facilitates PI planning?
Release Train Engineer4. It is Led by a Release Train Engineer who is a Servant Leader for the Agile Release Train. The Release Train Engineer is at the front of facilitating the PI Planning session and ensures that a seamless and smooth PI session is done.
What is the difference between sprint and Pi?
It's simple: PI Planning happens between teams. Meanwhile, Sprint Planning is an event for team members. The main difference is the scale and hierarchy – Sprints are a subset of PI Planning. Also, Sprints are made for a single Sprint.
WHO removes impediments in scrum?
the Scrum MasterThe Scrum Master's main responsibility is to identify, track and help remove impediments. Often, team members remove their own impediments. Sometimes, Impediments are beyond the ability of the Team to remove. In that case, the Scrum Master may have to get support from outside of the Team.
What is MVP in sprint?
MVP (Minimum Viable Product), the Core of the Agile Methodology. An MVP is a concept from agile scrum that refers to a product that has just enough features to satisfy the needs of early customers and, more importantly, give them something to provide feedback on to shape the future of the product.
Who owns the Product Backlog?
the product ownerWho Owns the Backlog? While the entire cross-functional agile team works together on the backlog, the product owner owns it. In most cases, the product owner (or product manager) holds responsibility for organizing and maintaining the product backlog.
What is PSI SAFe?
A pre-site safety inspection (PSI) is an examination of a site before the project work begins. It includes the general observation of the overall conditions of the area, appraisal of compliance, interviewing personnel and examining the operability of specific works.
What is a hip sprint in Agile?
The HIP sprint is characterised by having no backlog items that provide new value and is purely devoted to the activities described above. Allowing time for these activities during the HIP sprint means that the development cadence can be maintained year around, with no special scheduling adjustments required.
What is a sprint backlog in Scrum?
A sprint backlog is the set of items that a cross-functional product team selects from its product backlog to work on during the upcoming sprint. Typically the team will agree on these items during its sprint planning session. In fact, the sprint backlog represents the primary output of sprint planning.
When is a SAFe PSI not a PSI?
Over the last couple of months, I have delivered the Leading SAFe course half a dozen times to a diverse set of companies and audiences. Whilst some groups had already been investigating SAFe and some were seeing it for the first time, common areas of confusion emerged.
Deliver after multiple PSI's
Whilst every seasoned agilist shudders at the thought, the reality is that many scaled solutions run 12-18 month cycles prior to delivery. I often encounter this with solutions involving multiple enterprise-grade COTS applications (eg Siebel, SAP, Amdocs).
Deliver each PSI
This is the initial interpretation I see people most commonly make of SAFe, although in reality I've never actually known a train that implemented it. At this point, of course, the PSI acronym begins to break down. It is no longer a "potentially shippable increment", because it is in fact a " shipped increment ".
Deliver when ready
Everybody I speak to at least aspires to this model, and it is certainly the closest to my heart. The delivery cycle is completely detached from the planning cycle. Features are released as and when my business/customers are ready. Of course, at this point the PSI is no longer a PSI. We are now simply running a planning increment.
Conclusion
I like to begin with the end in mind. In this day and age, regardless of scale and technical platform continuous delivery should be the aspiration. For most scaled scenarios, however, the majority of companies cannot initially do so economically.
What is an incremental in a sprint?
An Increment (sometimes referred to as a 'Potentially Shippable Product') is the value delivered for the customer via the Product Backlog Items completed during a Sprint. Each Increment should interface seamlessly with all prior Increments and stand alone as a distinct addition of value to the Product. While more than one Increment may be created in a Sprint, all work must meet the Definition of Done to be considered complete. Last but not least, each Increment represents a concrete step towards realizing the Product Goal.
What is commitment of the increment?
The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. The moment a Product Backlog item meets the Definition of Done, an Increment is born.
The MVP
You’ve done your research, you’ve walked customer focus groups through a few rounds of Buy a Feature, and you’ve made some decisions around what your next release might look like. In fact, you’ve engaged your marketing team and you’re iterating through ideas about how to make a big splash – ads in trade magazines, promoted Tweets, Facebook posts…
The Lean Startup Conundrum
In his book “The Lean Startup”, Eric Reis confusingly re-defines the term “Minimum Viable Product”, which he explains in an interview in 2015. In short:
All About the Learning
That nagging voice in the back of your head, wondering if there’s a way out of the Analysis Paralysis trap you’re in, trying to figure out a way to actually know the answers to some of your questions, instead of analyzing yourself into a deeper sense of false security? That’s where the Minimum Viable Product comes into play.
How often should I have a PI meeting in Agile?
It is mandatory to have a face-to-face PI planning in agile meeting every 8 to 12 weeks which will certainly pave way for team communication. When the entire team meets they will understand things better and can brainstorm challenges.
What are the challenges of Agile?
Though, Agile principle says, face to face communication, it becomes practically impossible to have face to face communication. If bringing everyone on the same page is the first challenge, then keeping all the remote teams interactive and focused is another big challenge. Though, video conferencing can help make it possible to connect, but still it remains the challenge.
What is PI planning?
PI Planning full form is Program Increment Planning. PI Planning is one of the most important ceremonies of SAFe implementation. Program Increment (PI) Planning is the core of the Agile Release Train.
How many sprints are in PI planning?
Sprint Planning is done for the single Sprint whereas PI planning is done for four sprints together to get a vision of business value. Sprint planning is done once in either 2, 3 or 4 weeks at the beginning of the Sprint depending upon the sprint length.
What are the inputs and outputs of PI planning?
Following are the inputs to the PI Planning: 1. Customer should be ready with what he needs from the Program. The context needs to be set and ready. Basically, the in-scope items, its priorities. 2. Product Owner or Client should be ready with Roadmap and goal. 3.
What are the steps of program increment planning?
Similarly, following are the steps for Program Increment Planning: 1. Preparedness at Organization level: Preparation must be done at the organization so that the client, managers, product Owners can attend the PI Planning especially when we know in advance of any upcoming PI Planning meetings.
Preparation
PI planning is a significant event that requires preparation, coordination, and communication. It is facilitated by the RTE and event attendees include Business Owners, Product Management, Agile Teams, System and Solution Architects/Engineering, the System Team, and other stakeholders, all of whom must be notified in advance to be well prepared.
Standard Agenda
The event follows an agenda similar to Figure 2. Descriptions of each item follow. For guidance on adapting this agenda to support planning across multiple time zones, refer to the advanced topic article, Distributed PI Planning with SAFe.
Solution Train PI Planning
This article focuses on the planning activities of a single ART. However, large Value Streams may contain multiple ARTs and suppliers. In this case, the Solution Train provides coordination using a Pre-PI Planning event, which sets the context and provides the inputs for the individual ART PI planning events.
