(Last updated: Jan 27, 2002)
|
OPEN |
||||
|
ID |
Priority |
Component/Issue |
Proposed Resolution |
Responsible Person |
|
21 |
High |
The policy for localizability for Forms is unclear (i.e. do they need to be localizable for Suite V2?) |
|
Frank, Lee, Ed |
|
22 |
High |
The ability of products to upgrade easily from release to release and beta to release is uncertain |
Document the upgrade path, and evaluate the awkwardness. |
Engineering managers |
|
15 |
High |
For the components, what are the build procedures in general, and specifically how do we handle inserting documentation into the build |
Move the build to Nashua, restructure the way documentation is built and hooked into context sensitive help. This is in progress. |
Randy, Allen, Bob, Jake |
|
10 |
High |
Technical Writing is on a critical path, and does not have sufficient resources |
Hire additional writers. A signed PO is in hand with permission to tender an offer. |
Randy |
|
19 |
High |
Delays in ordering multiple processors will delay resolution of stability problems with component A |
|
|
|
14 |
Low |
Need to set up beta program |
Our beta program will be reactive, rather than proactive, |
Stan |
|
CLOSED |
||||
|
ID |
Priority |
Component/Issue |
Proposed Resolution |
Responsible Person |
|
3 |
Medium |
Low bandwidth from Product Marketing Management for myriad product direction details |
Some activities
can be moved to engineering project manager:
For other direction-setting will come from product management |
Frank, Lee. |
|
12 |
Medium |
Once we have schedules for rebranding builds, the writers need to re-evaluate the impact of rebranding on the writing process (especially screen shots |
This has now been factored into the documentation task estimates. |
Engineering managers, writers |
|
4 |
Medium |
Configuration requirements of WebForms and Flow integration not fully understood |
A “Deployment Configurations” document has been written and approved |
Stan |
|
18 |
High |
Customer commitments have been made for Component B 4.3 at the end of January. |
Shipped to Dan |
Frank, |
|
11 |
High |
Testing of Component A is on a critical path |
|
Sue |
|
17 |
High |
Due to complexity, some components that require testing on Component B must be assigned to specific resources that are already on the critical path. |
Reflected in the schedule |
Sue, Stan, Frank |
|
20 |
High |
Phase I did not ship until 12/21/2001, which in turn delayed the start of testing for V2 |
Reflected in the schedule |
|
|
7 |
Low |
Are Component C and Component D to be included on the Autorun menu |
C: Yes, D: No |
Ed |
|
8 |
High |
Testing of Component A is a critical path |
Have Peter develop test plans, then enlist Becky and Jake to help. Pending feedback of replan |
Sue |
|
5 |
High |
Synchronization of Component A plans with Suite |
Subset original Component A plans to accommodate Suite schedule |
Bob, Nabil |
|
12 |
Medium |
Once we have schedules for rebranding builds, the writers need to re-evaluate the impact of rebranding on the writing process (especially screen shots |
This has now been factored into the documentation task estimates. |
Engineering managers, writers |
|
16 |
High |
Is Component Y part of the Suite and if so, to what extent (e.g. is it on the autorun) |
Yes, it is one of the pieces of Component B, and as such is installed with Component B, so does not have a separate install. |
|
|
1 |
Medium |
Forms - uncertain resource levels - 2 people on maternity leave |
Assume Li is not available, and Paula not available after 1/2/2002 |
Sue |
|
2 |
Medium |
Level/Depth of rebranding |
Agreement will be documented in Ed's Rebranding guidelines and posted on the engineering web site |
Stan |
|
6 |
High |
Are Components C, D, and E part of Suite V2.0 |
C (Yes V6.1), D (Yes V4.3) and E (Yes V4.3) |
Ed |
|
9 |
High |
Dick's development is a critical path |
Defer Selected bug fixing; delay some documentation until after code freeze |
Stan, Lee & Helen |
|
10 |
Medium |
The aggressive schedule does not permit enough time to respond to feedback from beta sites |
|
|
|
13 |
Low |
The install of the integrated Component B is different from the stand-alone install (the Suite autorun used command line switches for Phase 1) |
For all components in V2.0, the install of the individual component will include the same functionality whether it is intended to be used with the rest of the Suite or stand-alone, so that the Suite CD can be used to install a stand-alone component and integrated components can also be used stand-alone. |
|