Updating a project charter

[brianraymor]

Once there is more experience with the charter process, we should review the scenarios where updating a charter is recommended or required. In practice, the scenarios tend to include:

• A project has completed the specific milestones in its original charter and proposes to add additional milestones.
• A project is unable to complete the work outlined in its charter.
• The charter assumptions have been modified by experience.

Depending on the outcome, we can assess how lightweight the process should be. For example, adopting a process similar to Kubernetes would allow a project lead to approve charter updates that are internal in scope.

Changes to charter/README.md:

1. Rename What the process is to Creating a project charter
2. Add Updating a project charter

[brianraymor]

Notes from PM F2F (9/25/18):

• Ensure that previous charters are archived for review (for earlier scope as an example)
• If the scope of the charter is increased or decreased then the charter MUST be reviewed and approved again by the appropriate Oversight team (Arch++ or PM++).

[brianraymor]

RFC2418 Charters:

   Charters may be renegotiated periodically to reflect the current
   status, organization or goals of the working group (see section 5).
   Hence, a charter is a contract between the IETF and the working group
   which is committing to meet explicit milestones and delivering
   specific "products".

RFC2418 Rechartering a Working Group:

   Updated milestones are renegotiated with the Area Director and the
   IESG, as needed, and then are submitted to the IESG Secretariat:
   [email protected].

   Rechartering (other than revising milestones) a working group follows
   the same procedures that the initial chartering does ...