RE: charter update with two year cycle

From: Alastair Campbell [mailto:acampbell@nomensa.com]
Sent: Thursday, October 6, 2016 10:55 AM


It seems like the trick to chartering is to specify as little as possible, in which case that seems sensible…



[Jason] Agreed.

Also, re-assessing what you’ve learned before the next ‘sprint’ (e.g. starting 2.2) might be considered quite agile ;-)



[Jason] Yes, except that one of the options on the table would be not to pursue agile development at all and to move directly to the next major revision.



________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________