 |
|
|
 |
|
|||||||||||||||||
|
|||||||||||||||||
 |
Project Managers Status Reports.
|
|
|
3/4/01 Progress Report Week End #9
Everything is looking good so far. We released R3 to the customer on Friday with zero known bugs. All features have been implemented with the exception of Find. There was not enough time to do it. I feel very confident about this release, as we have been doing much better than for the second one. I have kept us on track for the most part and made sure that we do not get behind schedule very much. Now all that is left to be done is compile all of our documents to be turned in on Tuesday, and make sure all pages on the web are updated. We will go over all this on our Monday night meeting, as well as go over the Release 3 Checklist to make sure that we do not forget anything and that we are thoroughly prepared for the final release on Tuesday.
3/4/01 Progress Report Week End #8
We have made some good progress on our coding this week, and I feel our program will be in good shape soon. All functionality must be done by Sunday so we can start testing. We are still a day behind, as Find is not done yet. All other functionality, such as binary file, delete key, and the help system have been implemented. I see improvements in out coding, as most of us have been accomplishing a lot without relying on the help of Chris. This allows Chris to work on his own modules with fewer interruptions. Our scheduled coding sessions have saved the team, in my opinion. We work much better when we are all together than when we code individually at home. Scheduling conflicts have been a problem for a few team members though.
We are lacking on our testing. We have our testcases documented, although nothing has been automated yet. We were having problems getting JUnit to work properly. Our visibility has been updated through the week's end, so once we pick up a few loose ends, we will be able to enter testing mode.
2/25/01 Progress Report Week End #7
We have finally sent out Release 2 and got it back with some problems. With new job assignments, we all discussed our strengths and weaknesses. To keep us on schedule, I have set up 3 team coding sessions a week to keep team momentum going forward. All of us need to improve our coding skills, because we cannot rely on Chris as a 'hero'. We have recalibrated our estimates based on the visibility from release 2 and have determined that we can produce about 200 lines of code for release #3. We are a few days behind schedule as we have found that some of the coding is tougher than we expected.
2/8/01 Progress Report # 3
We have completed about 90% of our web page updating, but have hit the 90/90 problem and are currently about 3 days behind schedule. We plan on delivering our release 2 to George tonight or tomorrow. We received one anonymous feedback suggesting that we move our anonymous feedback channel be moved to the bottom of our website which we are currently doing. We have hit some of our mini milestones but still had some incomplete action items that need to be taken care of. A meeting is going to be set this weekend to hopefuly catch up a little to get back on schedule.
2/1/01 Progress Report # 2
Our web page needs updating, but most documents exist on paper and just need to be posted. We have walked through 3 of the 6 features we are implementing for this release. We set two meetings for this weekend to hopefully complete all the walkthroughs and as much of the testing as possible. Right now, we are about 1-2 days behind schedule and hope to make up that time this weekend. We set up Dreamweaver for web page updating and I essentially assigned the entire web site and all of its components as an Action Item to be completed by 2/2/01 at 8pm. Each person has about 3 documents they are responsible for that either need to be updated or completed.
1/25/01 Progress Report # 1
So far we are on schedule, and have not discovered any defects except the residuals on the toolbar. We have completed all mini milestones, and have received no feedback from our anonymous feedback channel. We need to update our visibility and schedule, but have got our cvs online. Finished corrections to release one components as well as about 10 other documents on the web page.
3/6/01 Updated
Week 8 report, Tony Tomarchio
2/27/01 Updated Week 7 report, Tony Tomarchio
02/08/01 Moved Time Logs to separate link
02/08/01 Added this weeks rpt.
02/05/01
Updated TimeLog, Tony Johansen
02/01/01
Current Time Log Added, Tony Johansen
