Ticket #1586 (closed unplanned_task: obsolete)
UNPLANNED_FEATURE_SCHEDULE_R0
| Reported by: | deyan | Owned by: | sriggins |
|---|---|---|---|
| Priority: | major | Milestone: | M02b_PRE2b |
| Component: | PROJECT_COMMUNITY | Version: | |
| Keywords: | Cc: | ||
| Category: | unknown | Effort: | 2 |
| Importance: | 99 | Ticket_group: | |
| Estimated Number of Hours: | Add Hours to Ticket: | ||
| Billable?: | Total Hours: | ||
| Analysis_owners: | sriggins | Design_owners: | sriggins |
| Imp._owners: | sriggins | Test_owners: | |
| Analysis_reviewers: | pap,boyan,boyan | Changelog: | |
| Design_reviewers: | deyan | Imp._reviewers: | kyli |
| Test_reviewers: | sriggins | Analysis_score: | 3 |
| Design_score: | 4 | Imp._score: | 3 |
| Test_score: | 3 |
Description
Change History
comment:1 Changed 16 years ago by sriggins
- Status changed from new to s1a_analysis_started
- Analysis_score set to 0
- Test_score set to 0
- Design_score set to 0
- Owner set to sriggins
- Imp._score set to 0
- Analysis_owners set to sriggins
comment:2 Changed 16 years ago by sriggins
- Status changed from s1a_analysis_started to s1b_analysis_finished
comment:3 Changed 16 years ago by pap
- Status changed from s1b_analysis_finished to new
- Analysis_reviewers set to pap
- Imp._score changed from 0 to 2
- You should stick to the task page template. It is very important to fill all the sections and not to delete any of them.
- The "Task requirements" section is the most important as it is the one that is used to verify that the design and implementation are correct.
- You can create a page using the template when creating a new page. There is a drop-down list of the available templates. Choose TaskPageTemplate.
- What you have done in the main Analysis section is what most likely should go in the requirements section
- The requirements should be exactly what things you expect to be available in the result.
comment:6 Changed 16 years ago by sriggins
- Status changed from s1a_analysis_started to s1b_analysis_finished
comment:7 Changed 16 years ago by boyan
- Status changed from s1b_analysis_finished to new
- Imp._score changed from 2 to 0
- Analysis_reviewers changed from pap to pap,boyan
- Analysis_score changed from 0 to 2
Here are some things to improve:
- I think we should try to be more specific about the features included in each release.
- You should specify what exactly the result will be - I think a wiki page is the best option, because all our documents are in the wiki - write this in the Task Result section.
- The implementation idea should provide example on how you may approach the task - how will the information for determining the schedule be collected, for example?
- You may add links to the wiki pages of the other schedule related tasks about (their names start with UNPLANNED_FEATURE_SCHEDULE) to the Related section.
- Better way for demonstration is showing the document to the team, not only providing a link (someone can miss it) - provide this in the How to demo section.
- You do not need to add anything to the Testing section (just as you do not write anything in the Design and Implementation sections) when you are doing an analysis.
comment:9 Changed 16 years ago by sriggins
"I think we should try to be more specific about the features included in each release."
THAT IS THE OUTCOME, NOT PART OF ANALYSIS
"You should specify what exactly the result will be - I think a wiki page is the best option, because all our documents are in the wiki - write this in the Task Result section."
Nick decides this, not me.
THis stuff seems like such nitpicking to me, 6 DAYS to get a simple schedule task approved..
comment:10 Changed 16 years ago by sriggins
- Status changed from s1a_analysis_started to s1b_analysis_finished
comment:11 Changed 16 years ago by boyan
- Status changed from s1b_analysis_finished to s1c_analysis_ok
- Analysis_reviewers changed from pap,boyan to pap,boyan,boyan
- Analysis_score changed from 2 to 3
It is better now.
comment:12 Changed 16 years ago by sriggins
- Status changed from s1c_analysis_ok to s2a_design_started
comment:13 Changed 16 years ago by sriggins
- Status changed from s2a_design_started to s2b_design_finished
comment:14 Changed 16 years ago by deyan
- Design_owners set to sriggins
- Design_score changed from 0 to 4
- Design_reviewers set to deyan
- Status changed from s2b_design_finished to s2c_design_ok
Design is fine. Don't forget to fill your name in owners section.
comment:15 Changed 16 years ago by sriggins
- Status changed from s2c_design_ok to s3a_implementation_started
comment:16 Changed 16 years ago by sriggins
- Status changed from s3a_implementation_started to s3b_implementation_finished
comment:17 Changed 16 years ago by kyli
- Status changed from s3b_implementation_finished to s3c_implementation_ok
- Imp._owners set to sriggins
- Imp._score changed from 0 to 3
- Imp._reviewers set to kyli
3p. I think it is acceptable.
Please, fill your name in owners section!
comment:18 Changed 16 years ago by sriggins
- Category set to unknown
- Status changed from s3c_implementation_ok to s4a_test_started
comment:19 Changed 16 years ago by sriggins
- Status changed from s4a_test_started to s1c_analysis_ok
- Test_score changed from 0 to 3
- Test_reviewers set to sriggins
comment:20 Changed 16 years ago by sriggins
- Status changed from s1c_analysis_ok to s3c_implementation_ok
comment:21 Changed 15 years ago by deyan
- Status changed from s3c_implementation_ok to closed
- Resolution set to obsolete
Batch update from file query-obsoleted.csv
Note: See
TracTickets for help on using
tickets.
