Comments on the Problem Statement draft: Document structure

[Jari Arkko]

Charlie Perkins wrote:
> 
> Hello folks,
> 
> I have some comments on the draft.  I'll break it down into
> three different e-mail messages, because otherwise I am
> afraid that many points might be lost.
> 
> I believe that the document structure causes the
> document to lose effectiveness.  It can be improved by
> some pretty basic reorganization:
> 
> - The "Changes" sections should be moved into an
>   appendix (or multiple appendices)
> 
> - The "Acknowledgement" section (currently 1.4) should
>   be moved to be the last section before the normative
>   references.
> 
> - In Section (2), the first part of the section should
>   itemize the list of root causes, e.g.:
>   = Unclear Mission
>   = Poor Use of Effective Engineering Practice
>   = Standards Process Abuse
>   = Workload exceeds available staffing levels
>   = Unsuitable Management Structure
>   = Poor WG dynamics
>   = Inadequate Staff Preparation
> 
> This text should be placed before section 2.1.

Agreed. Note that we should probably publish this document
as soon as possible, and get to the next step (see the thread
about needless continuous refinement). But the above modifications are
very easy and they should be done to get the point across
better.

--Jari