Third article on the Boooksprint that took place at the end of 2016 with the Boooksquetaires Goood!.
This day was to be marked by 2 events: the delivery of our first increment and the departure of Grégory, our Boooksquetaire from Lyon.
It is therefore with great enthusiasm that we begin this second part of PI #1. Good reading ! 🙂
The Boooksprint article series:
- Boooksprint: boarding the Agile Rocket
- Booksprint: at the heart of PI # 1 (Part 1)
- Booksprint: at the heart of PI # 1 (Part 2)
- Booksprint: The Distributed Team Experience
- Booksprint: end of the adventure
9.00 – Planning the day
Our second day of PI #1 starts and we have to think about the evening landing to have a first increment of product. Christophe tells us that he has carried out a first proofreading of the various modules and that we have things to modify. In addition, his part on the "Flux" is awaiting proofreading.
Our organization is therefore heading in this direction:
- Christophe will start to process the “North Star” module while waiting for the proofreading of his part on the “Flux”
- With Julien we will continue for a moment on our part to homogenize with the “Visual Management” module in which we will also have to insert some of our parts. We will then switch to proofreading mode to be able to validate the first modules.
- Arnaud and Gregory will advance on the content of their game, feeling that they may be a little behind.
9.15 – Here we go again!
We settle in and let's go! Julien will proofread and comment in order to improve the way in which we introduce the different subjects. For my part. I restructure our content based on a style and structure that is as homogeneous as possible with our colleagues in Visual Management.
Little by little, ideas are coming up and this makes me want to add details, details, links... but I feel that Julien is not on his plate: he would like us to work together this morning to have a shared understanding of what has been written. We are reworking our writing style a little bit to go from simply describing a theme or tool to explaining the intention behind this theme or tool. This satisfies us much more because it provides the reader with a meaningful perspective!
However, I feel that the energy is not there: we may not have the same rhythm. We skate a little bit until we get to our first stand-up.
10.30 – Synchronization
This stand-up was welcome. Indeed, after having mentioned the difference in rhythms that we could individually have with Julien, it was Arnaud who spoke about his difficulty in starting this day. The time to get into his subject and the synchronization point cut him off: a rhythm problem once again.
It was perhaps time to change our mode of organization to restore some momentum:
- Grégory and Julien will then start working together on the History parts of the 2 modules,
- Arnaud will continue alone on his side to put his ideas,
- For my part, I will finish the few additions made in my game and switch to replay mode.
11.15 – Looking for feedback
To obtain external feedback, we invited our colleagues Goood! to look at the state of our current production.
Good luck ! I started looking at what you had already produced, it's great!
It's hard to get more feedback on a Sunday, but it's already a good start! We will then try again during working days.
Note: Note that the Gooodiens are part of the personas defined in sprint 0 aka "Kouigna Man".
11.30 – Retrospective
The retrospective is this time hosted by Grégory. We start with the same format as before, here are the results:
What works :
- I'continuous improvement through exchanges, sharing and borrowing
- THE proofreading allow you to guide the rest of the writing
- THE collective individualities : using diversity as a strength
What we need to change :
- Management of pace : more individual writing time for some
- More than dynamism in Stand-ups to limit the time
- More'examples concrete
Note: like any team, we learn from our strengths, our weaknesses but also from our differences. With respect for everyone, we have adapted our process so that individual qualities can be expressed within the collective.
It reminds me of this African saying:
Alone, we move faster, together we go further
This is the idea that I keep at this point in the adventure because depending on the dimension in which you want to move forward, the strategy adopted is not the same. Self-organization then works rather well! 😉
12.00 – Break
We really needed a little break by the sea to recharge our batteries! It had to be faster than the day before because we had a landing scheduled for this evening and the team was not particularly calm! Grégory's departure was coming little by little and we felt that he was frustrated at having to leave! 🙂
13.15 – Coffee schedule
Under the bright sun of this day, we plan the afternoon with once again our objective in mind: the delivery of the PI #1 with the Visual Management, Continuous Improvement, Flux and North Star modules. We decide to continue our momentum from the morning and see what happens at our next synchronization point.
14.00 – Last Sprint of Gregory among us
We set off at full speed after lunch to prepare for the end-of-day landing.
The Grégory and Julien pair seems to work well in the construction of stories and Arnaud is progressing rather well on his part. I continue on my side on the proofreading of the parts "Flux" and "North Star" to be able to consider them as finished. Christophe is beginning to prepare for the integration of the PI #1.
15.30 – Synchronization
Our Stand-up is very fast, we quickly share where we are, and we will focus on what is most likely to be completed for tonight. We then go into a phase of intensive proofreading and updates on the fly.
The energy is there, we all want to provide something tonight! We can then see comments appear and disappear, suggestions for improvement directly taken into account, a focused reactivity to allow us to finish what is closest to the release!
17.00 – Review
The hour of the review is already ringing and we can feel that the atmosphere is not at its strongest.
The observation: we will not be able to deliver everything we wanted, as we wanted.
What must absolutely be part of our IP? #prioritization
What do we think we can replicate for future Agile Rocket modules? 1TP5 Homogeneity
What can we postpone to the next version? #planning
We will have to make choices and it is not easy!
Our basic structure has therefore changed in this way:
Why this choice ?
Turns out we had some difficulty writing thestory after. Indeed, the tone often gave the impression that the results were magical, which was obviously far from our message. About the artwork, we started from the premise that the guide without illustrations was more valuable than illustrations without content. This would suit us for a first version but not for a paper print.
I have the feeling that we had evolved in the phase of Standards of tuckman model :
People feel part of the team and realize they can be successful together
if they accept other points of view
Forward for the PI #2!
For Grégory's departure at 6 p.m., we have 3 of the 4 modules ready and integrated: Visual Management, Flux and North Star.
Christophe jumps at the chance to celebrate this success with the bugle!
Note: The Continuous Improvement module still needed a little proofreading before it could be validated and integrated. He will officially be part of PI#1 around 7:00 p.m.
We crystallize this moment with a small group photo, announcing the start of a new adventure: the PI #2 will be done with one of our boooksquetaires from a distance ! 😉
Learnings
- THE respecting everyone's pace was key to ensuring good team cohesion and developing new ideas
- There solidarity members of the team made it possible to brave the difficulties together, without feeling isolated in one's corner
- There collective focus enabled us to finalize elements and continuous proofreading to standardize the content
- We had to review our plans after becoming aware of what we were capable of producing with sufficient quality
- There prioritization was essential to ensure a framework for the next PI
Next article: “Boooksprint: at the heart of PI#2 (Part 1)”
