|
Team Meeting Notes |
Tuesday 03-13-2001
Most of today's meeting was spent finding the cause of the mysterious 'robot-on-strike' error that prevented system tests from being run. After what was figured out, Dalbey met with us to go over our work and the Release 3 Checklist. Everything was in order, with only a few minor issues with Unit Testing and Software Inspection documentation raised. The last things left to do for our final project submission Thursday are to have the System Test scripts finished and to have the contents for the CD-ROM prepared.
Thursday 03-08-2001
Today we had a pre-release review with Dalbey. One of the most important parts of the release that we have to finish is to make sure that the User Manual and UI Prototype match the final product. We also have to make sure the Stage Delivery plan is in sync with the final product. Action items were assigned to people to take care of the last remaining differences between those three documents and the program.
We also talked about our release criteria and advised to do only enough work to meet the requirements (in terms of defects open, fixed) so that we can spend more time on getting the system test cases done. Dalbey also said it was ok to change release criteria #7 so that it applies only to severity 1 and 2 defects.
Tuesday 03-06-2001
Today we discussed everything that needs to happen in order to be ready for release next Tuesday. We originally thought all of our planned features for release 3 are complete, but we found one small feature that wasn't listed in the integration plan: having the buttons in the Object Pool be disabled when not usable. Phil has been assigned to code this.
The big thing left to do in the project is testing. The team was assigned to add minor changes to the code to help speed the testing process, such as keyboard accelarators and logging output to a text file. These changes, along with assigning System Test cases for others to create and perform, should help make Jon's job of testing easier. Once system test cases are complete we can devote the majority of our efforts to finding and fixing defects.
Thursday 03-01-2001
Today we discussed more of the details involved in performing unit tests. We've decided to use a modified version of the Assertion class listed in a Dr. Dobbs Journal article that pops up a dialog box with assert information. We also assigned non-trivial modules for everybody so they can prepare for the unit testing session Saturday.
In our change board meeting we came up with resolutions to requests 16 - 18.
Tuesday 02-27-2001
Today we came up with a finalized schedule that includes time for software inspections and unit testing. We also discussed how it would be best to move all the coding to be "complete" (inspected, tested, and integrated) by Saturday so we have enough time for testing and debugging. As a result we decided to meet Saturday morning in lab to do inspections on the code due Friday and unit testing on non-trivial modules.
We also assigned people to resolve/implement our approved change proposals.
Thursday 02-22-2001
Today we discussed the benefits of constructing, reviewing, integrating and testing new features incrementally throughout the rest of the project instead of coding a large group of new features and hoping they integrate nicely near the end. We've decided that the integration plan and schedule will need to be adjusted so that the features that we implement aren't all due at one day. This will make Jon's job of testing a lot easier since he doesn't have all his testing crammed near the release date.
The team also reviewed the customer feedback Wes obtained last night. Using the feedback we were able to finally resolve the outstanding change proposals we had left over from Stage 2. The changes that were approved require that more coding work be done, but not so much that it would have a significant impact on our schedule.
Tuesday 02-20-2001
Today we shared our answers from the Project Assessment assignment. Overall the team feels like we performed well during Stage 2, particularly with change control and meeting our deadlines. The things we feel we should improve are involving the customer in our project more, spreading the workload more evenly, and dealing with the feeling that we're not doing as much as we should be. The team also continued the process of transitioning into our new jobs by giving some pointers to those who are taking over our old jobs.
We also got back our Release 2 feedback sheet from Dalbey. To bring some of our release documents more up to par, we need to update the User Manual and Requirements Traceability Matrix to include more details about the requirements (currently, the documents contain more of a list of features than requirements). Wes and Phil have been assigned to update those two documents.
Thursday 02-15-2001
Today we didn't do a whole lot because we had a midterm in the morning. In lab we switched our roles. Our new roles are as follows:
The next week or so will be a period of transition into our new jobs and changing over from Stage 2 to Stage 3.
Tuesday 02-13-2001
Not much to report for today. We turned in a fully functional Release 2! Lab time was shorter than usual because all we had to do was turn in the stuff for our release. I think it went well.
Thursday 02-08-2001
Today we discussed everything that needs to happen in order to be ready for release next Tuesday. All of our coding is complete now for Release 2. The big push at this time is defect finding, tracking, and fixing. We are also updating documents to make sure they are standard with the rest of the project. Over this weekend we will be doing code walkthroughs. In lab today we discussed our code standard in regards to Dalbey's imposed exceptions and extensions in order that we are all following the same guidelines when doing these code walkthroughs. After this weekend all of our code should follow the same guidelines.
Tuesday 02-06-2001
In lab today we discussed where our project is since Release 2 is due in one week. We have almost finished the coding for Release 2. All of the assigned coding was complete but there are a few additional methods that we realized need to be completed. We have begun to log defects into Teamatic, but we need to devote a lot of attention to this over the next few days. Towards the end of lab we had a Change Control meeting for various requests (more information can be found by reading the Submitted Change Requests page). The requests were addressed and delegated to various people if they were approved.
Thursday 02-01-2001
In lab today we were happy to report that almost all of the coding for Release 2 is complete and our program has a lot more functionality (instant gratification). Our next focus is testing and as such we decided to begin system testing of the latest build, and we will have the test plan completed by next tuesday.
Tuesday 01-30-2001 Lab
In our lab today we discussed action items that were not completed and made arrangments to have them done by the next class period. We also discussed where are coding was in regards to the integration plan and release 2. Dalbey mentioned that we should number the requirements so that they are more narrow (like miniature milestones). Dalbey also said that he thought our training plan was good. The end of the lab was a time for everyone to ask any questions about the psuedocode, design, etc that we had.
Thursday 01-25-2001 Lab
Todays lab was shorter than usual because we did oral presentations during most of the lab. We discussed our Integration Plan and decided that we wanted to assign modules to be coded for Tuesday. We also had our first Change Control Board meeting in which we discussed possible changes such as how the session log will function. A more complete description can be found on the Change Control page.
Tuesday 01-23-2001 Lab
We discussed our Staged Delivery Plan and Integration Plan with Dalbey. We decided to rework our Staged Delivery Plan so that it makes sense for an external person. Along with this we decided to revise the User Manual so that it contains requirements numbers which we can then reference in the Staged Delivery Plan. As for the Integration Plan, this is currently being worked on and will be easy to finish once the Staged Delivery Plan is complete.
Thursday 01-18-2001 Lab
We demoed our Release 1 in class today. We decided to schedule a meeting of the main people involved with the design for Saturday to discuss the Stage Delivery Plan and Integration Plan. The Staged Delivery Plan and Integration Plan will be ready to show Dalbey on Tuesday. We also decided to use the web based bug tracking tool located at www.teamatic.com for our defect tracking.
Tuesday 01-16-2001 Lab
Formalized our Team Expectations. They are as follows:
We assigned the remaining jobs. Jonathon is the Risk manager and Wes is the Analyst/Customer Liason. We discussed what Release 2 may contain and decided that it should cover everyting on part 1 of the prototype. That will include loading in a class and instantiating it, as well as creating an object (ObjectPool will be fully functional). This plan has not yet been discussed with Professor Dalbey. Mike H. demonstrated that CVS is already functional and we decided to use it for Release 1. We decided to create a schedule showing when all of the members were free. The end of our lab time was spent assigning classes to team members for stubbing and preparing for Release 1.
Thursday 01-11-2001 Meeting with Professor Dalbey to discuss Design
Phillip, Jonathon, Mike H., and Mike P. all met with Professor Dalbey. We discussed our curent design and possible changes. Dalbey said that our design looks good as is, possible changes would probably require too much rework. Items that were brought up to be changed or implemented are as follows:
Other items that were brought up which may not be feasible were:
Thursday 01-11-2001 Lab
Lines of Code actual / estimates complete. Discussed what needs to be completed for Release 1 and began to assign work that needs to be done. Instead of working on a separate program for training in Java skills, we decided to assign parts of the GUI from our program to be worked on. We decided to have everyone think about team expectations individually and then discuss them on Tuesday. We also discussed the meeting format that we will use. In short it is as follows:
Tuesday 01-09-2001 Lab
Fetter Software received two new hires, Jonathon Lee and Apel Yahinian. We assigned roles as follows:
Phillip Hansen - Project Manager
Wes Strickland - Testing
Mike Power - Integration and Release, Training Coordinator
Mike Hebron - Configuration Management, Toolsmith, Web Developer
Apel Yahinian - Quality Assurance
Jonathon Lee - Designer
Team Meetings Notes page is maintained by Michael Hebron - Project Manager
Last updated 03/13/01