Difference between revisions of "Template talk:Development"
From Counting Opinions (SQUIRE)
| Line 40: | Line 40: | ||
==Testing== | ==Testing== | ||
| − | * Testing | + | * Testing plan as part of proposal |
| + | |||
| + | * Test form that can be added multiple times – Google Docs | ||
| + | |||
* Owner? | * Owner? | ||
* Due date | * Due date | ||
| − | |||
| − | |||
| − | |||
Revision as of 16:05, 7 August 2013
Contents |
To Do
- MagicNoCache Extension – add to summary pages
- New word for Development – Form & Status have same category.
- CSS for Tables
- Need Release Date
- upload image links
- field for customer who requested
Priority
- what is high/what is low
- 1 – High
- 5 – Low
- how do these get ranked
- Average?
- Total score
- weighted?
- IT first, Support Second
- Status, IT, Support, Alphabetical
Dates
- Delivery Date
- Release Date
Owner
- How do we track this
- Input – Page is created, Priority, Status, Owner change
- Proposed – Support Team
- Requested – IT Team
- Denied – Support
- Testing – IT
- Complete – IT – release date
Comments
add
Testing
- Testing plan as part of proposal
- Test form that can be added multiple times – Google Docs
- Owner?
- Due date
Summary pages
- if each step has an owner/due date?
- how to check off once they're done? – exclude based on status?
Status
- Looks like it is difficult to not include results
- master "project" category
- subcategories for each status?
- each status could have an owner/due date & complete/incomplete check box
__NOTOC__