On this page we transcribe and summarise the audio below.
http://transcript.thought.garden/assets/pre-planning-process/Pre Planning Process.wav Pre Planning Process
# Summary
The text discusses the importance of pre-planning meetings in Agile and Scrum framework, particularly in software development. These meetings are especially crucial for new groups embarking on a project where the standard procedures and culture may be unfamiliar. The key is to familiarize everyone with the flow, objectives, and potential challenges of the meetings. In addition, pre-planning meetings help to build consensus and ensure that everyone is aligned on the priorities for the week. The text further delves into the structure of these pre-planning meetings. Typically, the Scrum Master (or the engineer in this context) prepares the meeting by reviewing and organizing the backlog, then schedules a meeting with the captain (or project manager) to detail the agenda. This meeting ensures that the Scrum master and the captain are aligned and have a unified approach. The captain can also provide feedback and any necessary training to the Scrum master. The captain, Scrum master, and potentially the navigator then rehearse the actual planning meeting, ensuring they are prepared and comfortable with the upcoming tasks and agenda.
# Tidied Transcript
This audio note describes the pre-planning process in detail. I'll break it down into steps from a flow of consciousness perspective. The initial planning meeting at the beginning of the week is the most important and often the only real group meeting we have. We're beginning to add a review meeting as well. This is the initial or starting meeting that all new groups on all voyages need to conduct. For some, this is a new process, especially if they've never done software development or agile or scrum in an organization. It's an alien culture that requires a lot of explanation and work, hence the need for pre-planning. This audio note describes what that pre-planning is, not just the general pre-planning for starting a project, but specifically the pre-planning for the weekly meeting. In the end, when things are flowing, the scrum master, who is currently the navigator and the engineer splitting that task, will do the pre-planning. Given the classic bootstrapping problems that small groups starting without funding face, what is this pre-planning meeting? Why is it helpful? What's its purpose? What is its structure? The structure needs to be followed in detail. The pre-planning meeting should ideally take place a day or two before the planning meeting, after the review meeting. It involves the scrum master, in this case the engineer, spending an hour or two looking at the latest iteration of the backlog in the Osana project, figuring out the current priorities, and organizing the backlog. This is preparation for the pre-planning meeting. The pre-planning meeting should be on Saturday or Sunday if we're running the Monday morning scrum. The scrum master, the engineer, needs to schedule a meeting and invite the captain. It's essential that the captain goes through the plan for the scrum meeting step by step, offering feedback and possibly passing on training and knowledge about how to run that meeting to the engineer who hasn't run scrum meetings before. In the meeting, even if the scrum master is leading, they're doing it with the full support of the captain and the engineer. You don't want any difference in approach or opinion between the captain and the scrum master because that would mean the ship isn't sailing in one direction. In order to achieve that, you've got to go through the agenda of the meeting in detail in a Osana, in a Zoom call, discussing it with the captain. An hour's focus just on the task of planning the hour's meeting is appropriate to begin with. In the pre-planning meeting, the navigator should talk about the backlog and what they feel is currently going on outside of the world. The captain should give their input on what they feel should be the priority for the next week. Then it should go over to the engineer who's going to conduct the meeting and they should give their perspective on what they think is important that week. Once that discussion has happened, the final step is rehearsing. Go through the agenda and say how long each segment will be. This needs to be rehearsed in Zoom with the captain and possibly the navigator there. Then there needs to be a gap for the engineer to look at that, to think about that, and to be ready for the planning meeting on Monday morning. It's not good to leave it late into the Sunday evening. It's better to do it on the Saturday or on the Sunday and then have a breather before the planning meeting. It's up to the engineer to structure their own timing to make sure that it's not too pressured, but that it happens before the actual planning meeting.
# Keywords Agile, Scrum, pre-planning meetings, software development, Scrum Master, engineer, backlog, captain, navigator, training, agenda, planning meeting
# Graph
digraph { layout=fdp; "Agile" -> "Scrum"; "Agile" -> "pre-planning meetings"; "Agile" -> "software development"; "Scrum" -> "Scrum Master"; "Scrum" -> "backlog"; "Scrum Master" -> "engineer"; "Scrum Master" -> "training"; "engineer" -> "pre-planning meetings"; "pre-planning meetings" -> "captain"; "pre-planning meetings" -> "navigator"; "pre-planning meetings" -> "agenda"; "agenda" -> "planning meeting"; "captain" -> "planning meeting"; }
# Assets
pre-planning-process
# See also - Voice Notes
# Tools
The tools below will use generative AI to edit the contents of the page displayed above.
Tidy the raw transcript with generative AI: