SSE674Project4-Journal3

=Journal Entry =

=Week of 7 February=

We start our transition today and everything is crazy. We had some software progress and we feel confident that we will be closing out some of these processes soon.

=Week of 21 February=

We are closing our S-03, S-04, and S-05 at this point. We have seen the process is repair simulations and the software seems to perform as desired. We are giving our final approval to close these items out and will open up the repair items so we can start tracking these items.

Our engineering team is silent lately. They are not reporting any progress but I am sure it has something to do with the move to the new facilities. We are hoping it will ramp up production of the final guides we need to develop and get this project back on track.

Team Status

Management Meeting Status

=Week of 14 March=

It must be the action of breaking up the team, because we have repair drafts on the four remaining products. We are in the process of reviewing and signing off on the drafts. We should be seeing final products by the new deadline date of the April first.

We are also making progress on the software front. We are in the final steps of finalizing the backup and upgrade software processes. This will complete the development portion of the software phase and bring us right into testing phase. We are making great strides in this area to meet our deadline.

=Week of 4 April=

We are closing out the product guide risk, P-05, and are moving on into repair testing. Initial reports are looking good so we may be closing some additional risks out and be well on our way to completing the project on time.

Team Status

Management Meeting Status

=Week of 18 April=

We ran into another major snag. As our technicians were validating the repair software we discovered a major flaw in the software program. It doesn’t flow well with the design the engineers came up with and in the testing phase we did not consult the technicians to the point we needed to.

At this point we need to decide whether to stick with the current implementation and disrupt the flow of the repair process or go back into the design stage and re-work the software. We did a cost benefit analysis and here are the results

Project Home Next Section