[Bf-docboard] Being involved In documentation

[Michael Fink]

Hello team,

I know there has been a flurry of email traffic lately, so I'll try to keep this one brief.

I was surprised that nobody stepped up during a call for assistance that was made recently (I believe Campbell noted this in one of the emails, but I'm afraid I lost track of the conversations).  It made me wonder how many folks are on the mailing list vs how many folks participate?  This is a curiosity question, not a shaming one.  I've only made a single contribution to the wiki and it was just a minor correction to another person's much more involved effort, so I myself can't say I have been active either.


The point of this email:  it was mentioned that we needed a Project Manager to lead this effort.  I am not volunteering myself as I will not be able to devote the attention the Bf-docboard team deserves, but I am very earnest when I say that I am more than happy to help mentor the process.  (My credentials: I have been a Flight Chief for the US Air Force leading teams of 100+ individuals from all services and a wide range of ranks.  I have been a Superintendent of a Wing-level directorate responsible for planning and programming for 4,000 Airmen and directly managing a $19,000 annual budget and $20K in IT assets (not large, but sizable enough).  My job is Project Management, but not software project management or software development.  However, I am familiar with Agile methodology, Six Sigma, AFSO 21 as well as the more common "waterfall" way of doing things.)

I have built a template "Review" process.  The .pdf link is below as well as the .pptx--you are free to use this document if the team choses (use the slide master to remove my name and add the name of the person building the deck).  We have successfully used this process for several years to guide multi-million dollar projects impacting thousands of people across the globe.

PDF: https://www.dropbox.com/s/lwu6dhdn9hmcw63/Blender%20Documentation%20Project%20Review%20%28proposal%29.pdf?dl=0
PPTX: https://www.dropbox.com/s/pcorrecirwi9dos/Blender%20Documentation%20Project%20Review%20%28proposal%29.pptx?dl=0

It is useful for:
(1) Spurring discussion and ideas,
(2) Solidifying those ideas and discussion points into actionable tasks,
(3) Providing clear direction for those that are responsible for performing (or delegating) those tasks,
(4) Providing a method for updates and recommendations on existing tasks,
(5) Focusing a discussion onto a single vision and effort,
(6) and documenting progress, identifying trends, and adjusting effort quickly.

The "Review" does take time to update and build, but by consolidating tasks and inputs into a single document, it does help create a helpful overview and guiding document to manage the project--not just for the project leaders, but for all participants.  When we do these reviews, we consolidate inputs from as many as 30 offices and hold meetings to discuss the inputs and adjust focus or re-allocate assets (manpower, money, etc).  This is much more efficient than holding 30 different discussions, each with a meeting and side tasks--resulting in duplication of effort, starving some offices while overfeeding others, etc.  I think this is the best way to guide and lead a project of this undertaking.

Once the Project's goal is met (or solidly on track), the review process can end.  This is not meant to be a permanent fixture, but a simpler "metric" or "stoplight" document can take its place if desired.

Please let me know if you have questions on how this might help the project.  I am not knowledgeable on software (although I do play with HTML/PHP/SQL/etc), and I don't use Blender as much any more, but I am passionate about the community and what Blender represents, and I hope this is somewhat useful.

Thank you for reading, and sorry for the long-windedness.

v/r,
Michael Fink
BnBGobo99