David A. Wheeler
On Tue, 20 Jun 2017, Wheeler, David A wrote:Some projects don't plan to make any changes; some plan to make modestchanges; some plan to rewrite everything & the API is going out the window.
Yes, thanks, that helps. It does however make me question the value of the*Please* feel free to question! It's why this mailing list exists :-).
It asks for a document to be present that lists things that a projectI think this quote sums up things:
"Plans are useless, but planning is indispensable." - Dwight D. Eisenhower
As expanded here from DrupalCon:
"The value of a plan lies in the act and effort of planning: in doing so, you gain understanding ... Planning encourages situational awareness through learning and discussing strengths, weaknesses, opportunities, threats and a flexible strategy that can tie them all together. A good plan establishes a vision, with goals and supporting objectives, and provides context and directionality so the team can move forward and be supported without being locked in."
Clearly execution is *way* more important than just planning. But planning, and sharing your thoughts with collaborators, can increase the likelihood that everyone will work in the same (general) direction. Even just saying "we're in maintenance mode, and focusing on small incremental improvements" can help people understand things.
Also: In principle this criterion isn't difficult. Just figure out your current plan & write it down. The *real* challenge is the planning (to figure out your plan). The hope is that this criterion will encourage people to think that through; it encourages people to step back & think about the larger goals for the project.
--- David A. Wheeler