XM Planning and Review Strategy: Difference between revisions
Jump to navigation
Jump to search
(Created page with "So far, the only planning and review strategy involves these components on Flashy XM *Planning Survey sent to each developer every month, logged in database in Work Log wind...") |
No edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
So far, the only planning and review strategy involves these components on [[Flashy XM]] | So far, the only planning and review strategy involves these components on [[Flashy XM]]. | ||
*Planning Survey sent to each developer every month, logged in database in Work Log window, broken down by person | *Planning Survey sent to each developer every month, logged in database in Work Log window, broken down by person | ||
*Review Survey sent 30 days after Planning Survey, logged as Planning Survey | *Review Survey sent 30 days after Planning Survey, logged as Planning Survey | ||
*Default function of Control Panel is to visualize progress - by quantity of tasks completed in Panel | *Default function of Control Panel is to visualize progress - by quantity of tasks completed in Panel | ||
Tenure decisions should be made on: | |||
*Adherence to contract terms | |||
*Meeting Minimum Acceptable Performance standards defined in a person's contract on a monthly basis | |||
*Long Term Intent in contract involves participation through 2013 or 2015, the slated completion or infrastructure and slated completion of the GVCS 50 | |||
Suggested review meetings should include: | |||
*Assessment of month goals (Planning and Review spreadsheet) | |||
*Assessment of meeting long-term goals (quarterly, discussing trajectory through 2013 or 2015) | |||
Suggested Documentation Includes ready visibility of: | |||
*Contract published | |||
*Work Plan from contract published | |||
*Monthly Planning and Review | |||
[[Category:Flashy XM]] |
Latest revision as of 21:43, 5 August 2012
So far, the only planning and review strategy involves these components on Flashy XM.
- Planning Survey sent to each developer every month, logged in database in Work Log window, broken down by person
- Review Survey sent 30 days after Planning Survey, logged as Planning Survey
- Default function of Control Panel is to visualize progress - by quantity of tasks completed in Panel
Tenure decisions should be made on:
- Adherence to contract terms
- Meeting Minimum Acceptable Performance standards defined in a person's contract on a monthly basis
- Long Term Intent in contract involves participation through 2013 or 2015, the slated completion or infrastructure and slated completion of the GVCS 50
Suggested review meetings should include:
- Assessment of month goals (Planning and Review spreadsheet)
- Assessment of meeting long-term goals (quarterly, discussing trajectory through 2013 or 2015)
Suggested Documentation Includes ready visibility of:
- Contract published
- Work Plan from contract published
- Monthly Planning and Review