now after getting our program backlog ready and also exploring those program backlog item in the agile teams here the complete agile release train is getting together to conduct a pi planning meeting in this particular video i am talking about a tentative agenda for a pi planning meeting you can find one example of pi planning agenda at scale agile framework this particular tentative agenda is mostly inspired by something which is already there at scalechildframework.com you will know you will have your own pi planning agenda based on your own context but this agenda is a good starting
point to understand how possibly a meeting with hundred plus people can be run in an effective way and at the end of it we can come up with some integrated understanding of what as a whole agile release train we want to do in a bi so think like there are 125 plus people the complete agile release train group the business owners which is like key stakeholders the system architect product management all these people are coming and sitting together in order to do a pi planning meeting and your complete a child release train all group of
teams are also present for this particular large event now when all these people are coming together here we are starting with an example of two days of pi planning meeting agenda now this day 1 and day 2 gives us a good insight again it is just a default thing to start with 100 people sitting here or face to face or on a zoom call or in some other virtual tool call and they want to know how do we want to proceed in upcoming pi so first thing we need to do on a day one is
give them a big system view so everybody has a common understanding about opportunity ahead the milestones which are coming the technological approaches which we are going to take where do we stand at a given point in time all of us should be clear about it and that's why the initial section of day one is focusing on setting up the system view now there could be various ways of of setting up that particular system view you may have your executive coming in and talking about the business context what is happening what what is happening in the
competition what is happening in the market what all opportunities are coming to us and why this particular pi is important and how this particular pi event which which will help us in achieving something which the organization wants to achieve so we can't consider it as a strategic alignment how the work which this team is going to do is going to give organization a strategic advantage this helps us in understanding the overall context in which we are doing this pi planning meeting so once we get that particular strategic view we may want to go get into
a specific view our product management may come and talk about that the features which has been refined you should be already knowing them based on your agile team preparation time which you you have already done in your innovation and planning iteration but this is the place where you come to know about okay together let's explore this feature and understand what actually these features really mean so those top features which are candidate for our pi planning meeting may get discussed uh here there could be other things as well uh your system architect may talk about some
of the technological aspects some of the things which are already explored with the help of enablers or some kind of an exploration in the previous pi but this information and the learning has to be shared with everyone some recommendation for doing coding some recommendation for doing testing some recommendation for ensuring overall building quality in the agile release train there could be a change in definition of done there could be new infrastructure improvement which you need to consider while you are planning your work so those kind of a briefing is done by the system architect they
may share a lot of url talking about or a particular resource you can find there particular architectural ah related content you can find there the database table you can find those kind of links also get shared when the system architect may give their briefing now there could be other elements also there is a possibility maybe with the release train engineer or by some business owner may be presented some kind of improvement backlog items so in the previous program increment you did something there were some retrospective done and at the end of it at the end
of the pi you had an inspect and adapt event and based on that you picked up some items which you want to work on in this particular pi there is an improvement items may be a different way of doing things some kind of new guidelines for for doing development new guideline for integrating your work so those improvement backlog items which are planned for this particular pi may also get discussed in the in the initial system view of of setting up the stage for the whole pi planning you may also pick up things like the current
state of the product uh usually just before the pi planning meeting you already you see the whole demo demonstration of the integrated product uh in case that thing was not very well communicated it's a good idea to have a quick recap where we stand as a product yeah integratedly before we get into the pi planning details or a breakout level details at an agile team level so state of a product state of technical depth see its state of defects where do we the complete technological aspect may also get discussed in a system view so once
we are done with this particular section we each agile team is expected to know where do we stand and what we need to do in order to make this pi successful what are the milestones and what are the features or set of things will help us in achieving those milestones so we know what is expected from us and we also know where integratedly we stand then the release training engineer may come in and facilitate a team level planning so in order to achieve these features this work each agile team is expected to come up with
their part of plan now in this team breakout room the features which individual teams are picking up they need to get planned in a detailed manner so why i showed this kind of lines so it means they are these are the sessions which are happening in parallel so based on the discussion and our previous understanding dual preparation we had some features and now we need to work on those features by way of dividing those features into user stories you might have already done at a preparatory stage the a stage but this is the b stage
of of your user stories estimation planning dependency management and coming up with a plan for upcoming pi now when i say a plan for upcoming pi you can think like that in upcoming pi assuming i have a 10 weeks duration i may have eight weeks of development iterations which means i may have a four development iterations so when i need to come up with a plan for upcoming pi i need to come up with a plan for my upcoming four development iterations and as a team i should be able to figure out that by doing
these four iterations of development which portion of the program backlog i will be able to finish or which which part of my management expectation how do i help the management in achieving what they want to achieve from this particular program increment duration so that is why i am doing this breakout session and i need to come up with my team's plan for upcoming pi now this plan may have lot of interdependencies so in while i am doing this particular breakout sessions i do end up doing various integrated integration of my plans by way of talking
to different team and understanding how they are taking a particular dependency are they planning it in a given iteration if not i may want to point out that this will create a trouble for my my release or i need to understand what part of the the the feature like what all is getting included in a feature which other team has taken because i might be working on a feature and there could be some boundary elements which can go in that team which can come in this team also so our teams product owners may be continuously
talking to each other our team scrum masters may also facilitating the dependency exploration and integration while we are preparing this particular first level plan for upcoming pi so it's like this we got the big picture and each team got into separate rooms so you can visualize it that we have a big meeting happening all of us in were in the the big conference room we got briefed and once the briefing was done all of the agile teams went into separate rooms yeah and in those rooms they were planning their part of work in between there
were some scrum of scrum happening sometime the scrum masters were only doing it sometime team members are also moving from one room to another room to communicate about dependencies and issues as and when they are are discovering it if two teams are very closely working with each other they may decide to sit in the same room but have a separate tables so that they can more frequently talk to each other so there is no prescription for a format the room idea i am sharing just to give you a visualization that yes teams are doing their
part of work at the same time they are integrating their work as well and as a result of it they come up with a draft plan now while they are doing this thing they are doing velocity driven planning based on the team capacity or velocity they figure it out how many story points work they can do in upcoming four iteration they figure out the sequence of that work they identify the dependencies and those those things help us in identifying what this team can do in the given pi now once that is done they do a
presentation of their plan so the the next section if you want to take a learning from this breakout room and the first thing we do is called draft plan review so in this case think like this every team gets 10 or 15 minutes to present their plan and take some feedbacks and then go the next team comes in they present their plan and group of stakeholders who are playing the integration role may keep making points and they may realize that there are some gaps there are some capacity limits there are some technological challenges there are
some capacity challenges which needs to be taken care before we can resolve these issues so this draft plan review will help us in discovering lot of things there could be few teams which are unable to to do what was anticipated that they will be doing some features we were anticipating they will do but their load is is is too much there could be few teams who might be able to do the anticipated work in a faster time and they may have a capacity available there could be various dependencies coming between two teams because the way
teams are organized are creating lot of difficult dependency and maybe we need to reorganize these teams or make people move from one team to another team so those kind of issues may come as a as a result of draft plan review and based on that we may have a list released to an engineer may facilitate making that list and we will do something called management review and problem solving now many time i get this question who is this management and what is this management reviews happening so the skill that i don't give you an answer
who is this management you need to figure it out who is this management for your agile release train but the idea here is depending upon the nature of your work you may have some set of stakeholders who are expected to make decision here so that we can have a workable plan tomorrow yeah and that's the whole purpose of doing this pi planning meeting unlike in traditional way a one business department just gives their requirement and expect that the delivery team to figure out how to achieve it delivery team tells that we can't do it and
then this whole communication takes one month before some agreement can be raised here we are saying we are doing it together we have the delivery team available we have the the business owner stakeholders available here and they are coming up with their priorities and teams are coming up with their capacity but the balance has to be raised and in order to reach that particular balance both the group has to work together so this agile release train has to work together there is no one person who is saying we will do this or we will not
do this we need to collaboratively find out what can we do in order to have workable plan which adds maximum business value to the organization and how do we add to it in the upcoming pi so management driven problem solving and jointly we need to consider all problems as our problems dependency capacity uh skill gaps whatever it is we need to solve that and come up with some adjustments now during this time it is not necessary the whole team stays here some of the team members may go do go and do their homework for the
coming days and and but there are few individuals who may stay and finally come up with some decisions now once these decisions are made we start with second day so you can see the day one finishes by learning about what possible things each agile team can do and what are the areas which are not yet resolved and the resolution is getting proposed at the end of day one so we learned about their the team and their stage and we we have some adjustment identified now the day two start with those planning adjustments so it could
be change in priority it could be d scoping a particular feature and making it fit well in a particular time line for a particular team it could be moving one feature from one team to another team yeah so all these all options are open when to apply what option it depends upon the group which is reviewing and working together to come up with an and a workable api plan so we do planning adjustment so usually this planning adjustment might get communicated uh led by release train engineer maybe some business owner may be product management not
a particular person but we identify in your agile release train who is the one who can do this particular a job or a group of people may end up doing this particular job now once the planning adjustment get communicated we have a team breakout rooms again so the idea here is we again get into different different rooms based on our latest information learning from other teams we have been learning while doing breakout room as well but when we saw the draft plan of each team we learned more about them and based on those learning based
on these adjustments now we are reworking and maybe we also got some important idea about the priorities more details about the priorities and each team is reworking their plan and ideally by this time we have a good sense of what we are really trying to do and usually the release train engineers and scrum masters start continuously integrating the plan while the second breakout room is happening because there is a fair stability in understanding as well as solving this particular problem for coming up with an integrated plan for a for a pi so you do this
you uh the agile teams also get engaged continuously with the business owners when they are doing this particular activity and they work with them they take the business priorities for them and understand each the the part of the work which they are planning to do in upcoming pi their business value as well and with this we present the integrated plan again so more or less in the same way once the breakout room is over we have an integrated plan many time this integrated plan is not necessarily presented by team by team but it can be
presented together by the group of people where the whole plan is presented to the agile release train now here is again the collaboration happening now we have a plan and we have a business stakeholder sitting in the pi planning meeting do they see this plan workable and at the same time we need to make sure our teams see see this particular plan as an achievable so business feels that yes we can get our business priorities achieved by this particular plan and the development team feels that yes we can achieve this particular plan in a given
pi if that is there then we move forward if that is not there we need to do again problem solving and do a rework again ah if there are gaps there is a misunderstanding there are something which are critical but not getting fit into our pi we need to explore what can we do differently again we can't just say this is much priority i don't know if you you figure it out how to do it we need to collaborate will be work and there could be multiple iterations of identifying the problem adjusting the issue and
then again going in a breakout room there could be some cases where the problems may get resolved without breakout room as well but we need to have an integrated plan which is acceptable to business as well as coming from the development team where they feel they are good enough to work with it so assuming by doing few iterations we achieved an integrated plan which get reviewed then we talk about risks so while we were doing team level planning we do identify various risks and we do come up with possible approaches for those risk the focus
of risk here is more to do with risk on a given pi we are not talking about global risk and business risks here we are primarily focusing on what are the things which can probably details our pi plan so those risk and what what how many risk got identified and how we have resolved them mitigated them or we are planning to do something about them during the pi planning meeting we do a review of it so we share that particular information with the stakeholders now you might be wondering why are we doing it so everybody
understands how we are heading what are the chances we are taking because our business people will also be talking to their stakeholders and when they are communicating commenting committing some set of features they should know the overall uncertainty some amount of uncertainty which is there behind our pi plan so those uncertainties get communicated with the help of risk reviews there is a possibility in some cases some risks are not acceptable and that may also trigger a rework so there is a possibility of going back at any point in time but we do a risk review
and and related actions if there are any assuming the risks were acceptable and and that's the best judgment together we are taking business owners and development team then we move forward and we talk about a proper a kind of an exercise which helps us in checking the confidence of the whole agile release train for this particular pi planning so we take something called pi confidence vote so as you have learned the complete agile release 10 is participating here each each agile teams business stakeholders everyone is participating in this particular meeting so the pi confidence vote
is taken first at a team level so each team how confident they are feeling for their part of the work to get get achieved they are part of the commitments their part of objectives how how comfortable they are and then once we see a team level confidence coming in then we also take a program level confidence vote so how well how confident do you feel that we are going to achieve overall program level objective not only yours one but you see that the type of work has been planned the type of milestone has been planned
how confident are you in achieving that so we take a fist of five kind of what one to five one is less confidence and five is more confidence and if you have lot of less confidence that again can trigger a rework so we may need to rework till the time we have reached to a stage where we solve that confidence related problem and we are confident enough to go for this particular pi now you might be wondering there are too much cross checks and confidence checking and all see the idea here is this is an
event which is giving the direction to multiple agile teams who are forming a child release train and we we wish to do these kind of events once in a pi so there is a gap there is around 10 weeks gap so between these two two events we want to make sure that we provide sufficient amount of visibility and direction to the to the agile teams so that they can do their decentralized decision making and so that they can also integrate and align well with other teams so we do integrated plan review we do risk reviews
and we do we do take a confidence vote and if there is something missing we end up doing rework to come up with a workable pi plan finally we reach to a stage which is called planning retrospective so this retrospective is not a retrospective of your whole pi it is the only retrospective of pi planning meeting so you have been planning for last two days and you might have observed oh like we should have done this differently next time onwards we should have more breakout rooms next time onwards we should have these things cleared before
coming to a pi planning meeting or or you may realize that okay these debriefings are taking too much time can we optimize it by way of having some kind of email communication in advance so that debriefing can go faster or some kind of a gaps between breakout room or dividing the pi planning meeting in in three days or four days rather than running at stretch for for two days so there could be various ideas which can get compiled at the end of your first pi planning meeting if you are doing it first time and then
you refine the release train engineer and we take a lead in finding out how do we move forward with the new pi planning meeting now this was more or less focusing on the agenda part of it but if i summarize based on this whole agenda the input to a pi planning meeting which came here was more or less focusing on the refined program backlog items which are prioritized which are sized enough they fit well in a given pi for an agile release train that's a primary input there could be additional input talking about the technological
aspect talking about the current state of our product and talking about our improvement backlog items but the primary input is the prioritized program backlog now once we reach towards the end and we will explore those elements further further in our subsequent videos as an output we generate primarily two types of output one output is called pi objective so by the time we reach to a second breakout rooms and all each teams finalize their pi plan and they summarize that particular plan in the language which business can understand the language which is outcome oriented and that
is called team level pi objective so the team level pi objective shows what this team is intending to do in a given pi so that's a that's a one output comes in and then the the management released an engineer everybody work together to integrate team level pi objective at a art level pi objective as well so that's the the one output which get generated from this particular two days of pi planning meeting the second output which comes as a result of these two days of pi planning meeting is called program board we will explore it
in little more detail in the subsequent video the idea of a program board is understanding the interdependency between various teams in order to achieve pi objective so i have a objective to achieve and i need to visualize how i am dependent on each other in order to achieve that and i visualize it in the form of a dependency diagram which is called program board so this pi objective and program board starts getting prepared on the day 2 itself it starts from the draft plan review at itself and but in the day two they start getting
more and more refined and by the end of it each team has their pi objective and as an agile release train we have a joint pi objective as well as we have a joint program board which shows an integrated view for our upcoming pi you