Engagement/Integrated Marketing/Fleshing Out: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
Do you have an idea for a project? Great! Let's get started on helping you organize your thoughts so that people can understand why this idea is awesome. The purpose of the steps and resources below is to help you frame your ideas so that you don't have to start with a blank document. | Do you have an idea for a project? Great! Let's get started on helping you organize your thoughts so that people can understand why this idea is awesome. The purpose of the steps and resources below is to help you frame your ideas so that you don't have to start with a blank document. | ||
# [[Engagement/Integrated_Marketing/Fleshing_Out/Project_Brief|Designing your project brief]] | |||
# Getting your project brief approved | |||
## [[Engagement/Integrated_Marketing/Definitions#Deliverable|Deliverable]] is created, stored, worked on in a system of the team’s choosing. | |||
##A bug is created in bugzilla to track the deliverable | |||
##The deliverable is linked, attached, or directly entered into the bug. | |||
##A need info flag is added for each person who needs to approve. | |||
##Discussion happens either in face-to-face meetings (preferred) or electronic communications with approvers. | |||
##If approved, approver adds a comment “Approved” and clears the need info flag. | |||
##When all approvers have given their approval the bug is set to a resolved. | |||
##The deliverable is now in an approved state. | |||
Note: If the deliverable must be changed and re-approved the bug should be re-opened and the approval workflow repeated. |
Revision as of 00:08, 26 June 2014
Do you have an idea for a project? Great! Let's get started on helping you organize your thoughts so that people can understand why this idea is awesome. The purpose of the steps and resources below is to help you frame your ideas so that you don't have to start with a blank document.
- Designing your project brief
- Getting your project brief approved
- Deliverable is created, stored, worked on in a system of the team’s choosing.
- A bug is created in bugzilla to track the deliverable
- The deliverable is linked, attached, or directly entered into the bug.
- A need info flag is added for each person who needs to approve.
- Discussion happens either in face-to-face meetings (preferred) or electronic communications with approvers.
- If approved, approver adds a comment “Approved” and clears the need info flag.
- When all approvers have given their approval the bug is set to a resolved.
- The deliverable is now in an approved state.
Note: If the deliverable must be changed and re-approved the bug should be re-opened and the approval workflow repeated.