#Status Messages
Status messages should be sent first thing in the morning, before the developer begins work. They should list all projects that they're currently actively involved with, as well as any side items that need to be addressed. For all tasks that fall outside the scope of project work, or for direct feedback, a Housekeeping list item is recommended.
Messages should list the projects with their statuses at the top of each message. Underneath, include short descriptions of the status of each. The whole message should generally only be 5-10 sentences at most - be clear and to the point as much as possible. Make sure to list any items that are blocking you from completing work, and feel free to call out the responsible party.
Each project should list its status, from the following available options: OK (everything is fine and progressing normally), HOLD (waiting on something out of your control), WARNING (something has gone wrong here), DANGER (something has gone VERY wrong here), FEEDBACK (everyone in the message chain should read this and respond to these items to be able to progress).
When you receive a message, please try to respond to anything that arrives with the status of FEEDBACK that is relevant to you. Also, feel free to respond to other items that you might be able to help out on - especially for anything that is not OK.
A brief example follows.
Status 2010-07-03
- Newspage [OK]
- BetterCMS [FEEDBACK]
- Logo Image [HOLD]
Working on the Newspage app today, updating the homepage to match the new mockups from the designer. I'm also finishing up adding file upload support to BetterCMS today - if anyone has time to review commit #abcdef for any problematic issues, I'd appreciate it. Waiting to export our new Logo Image until the designer gets me the latest version.