Plan - co o tym mówi Scrum Guide?

Pracuję ostatnio nad tym, żeby planować i robić plan. I już rzeczywiście pojawia się rozmowa na temat tego CO będziemy robić następnego dnia, ale ciągle odwlekam jakąś taką formalizację planu jako fizycznego bytu. A bądźmy szczerzy - potrzebujemy tego, przynajmniej w moiej rodzinie. Gdy coś jest napisane (narysowane), to wiadomo, że jest ustalone, a jak tylko o tym rozmawialiśmy, to zbyt łatwo można o tym zapomnieć, pominąć, zmienić.
Postanowiłam więc sprawdzić co na temat tego jak powinien wyglądać plan mówi Scrum Guide.

Podsumowując
Nie ma tych informacji zbyt wiele, pewnie sposób na fizyczny Plan jest serią dobrych praktyk. Scrum Guide mówi za to dużo o jego cechach.

A poniżej 
Oryginalna treść Scrum Guide - fragmenty, w którym było coś o planie i planowaniu

• Each Sprint has a goal of what is to be built, a design and flexible plan that will guide building it, the work, and the resultant product increment.
• The work to be performed in the Sprint is planned at the Sprint Planning
• This plan is created by the collaborative work of the entire Scrum Team.
• The Product Backlog items selected for this Sprint plus the plan for delivering them is called the Sprint Backlog.
• The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.
• However, enough work is planned during Sprint Planning for the Development Team to forecast what it believes it can do in the upcoming Sprint.
• Work planned for the first days of the Sprint by the Development Team is decomposed by the end of this meeting, often to units of one day or less.
• By the end of the Sprint Planning, the Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment.
• At it, the Development Team plans work for the next 24 hours.
• The Development Team or team members often meet immediately after the Daily Scrum for detailed discussions, or to adapt, or replan, the rest of the Sprint’s work.
• The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.
• Create a plan for implementing improvements to the way the Scrum Team does its work.
• During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of “Done”, if appropriate and not in conflict with product or organizational standards.
• The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum.
• This emergence occurs as the Development Team works through the plan and learns more about the work needed to achieve the Sprint Goal.
• When elements of the plan are deemed unnecessary, they are removed.
• The Sprint Backlog is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint, and it belongs solely to the Development Team.