SE 300 Software
Engineering Spring 2005
Developing and
Executing a Plan:
Practice and History Web Searches
Plan and Legacy
TEAM 1 - TEAM MEMBERS RANDALL
FOOTE and PAUL PICAZO
Plan
Strategy
for dividing up the work
- The best at each task leads the task with other team members
supporting or working on different task they are better at. In
this case one team member researches while the other does the
documentation and if one team member is idle he will help the other.
Steps and estimated
time.
- Create Plan document (5 minutes)
- Search for reference websites (10 minutes)
- Document Websites (20 minutes)
- Create Record while documenting (20 minutes)
- Post documentation in a website (10 minutes)
- Create Legacy document (5 minutes)
A measure
of
completion, including quality and quantity. How will you know
when you're done? How will evaluate
results?
- We are done when all members of the group are satisfied with the
results or when no members are willing to take the time to improve the
lab. To evaluate the group will read the web page and decide
whether it meets the requirements.
Record
time spent on
each step (actual):
- Create Plan document (7 minutes)
- Search, Document, Record and Posting happened at same time(50
minutes)
- Create Legacy document (20 minutes)
defects
and mistakes:
- The middle steps got blended together because of
multitasking. While one of us typed the information the other was
researching and documenting. The failure was in the
communication. If one of us was need the other to translate the
research but the other was not in position to do so there was a lose of
productivity.
communication
problems
- As listed above with two people working on two different thing
there can be large productivity issues
Legacy
productivity (did
well/wasted time)
- The plan creation took a bit because we had to discover the
natural rolls of the members and then creating the plan based on each
members situation.
- The split plan was scheduled to take 10 more minutes then the
implemented plan took but both members did not learn all of the lab
only a pieces.
- The legacy was produced by one member which saved the issue of
argument, but took longer.
assessment of
quality - got good/results
- The quality of the work seems to be of that desired by the lesson
for all steps
evaluation
of your plan, e.g. steps missed
- Steps 1 and 6 stayed in place but everything else just got merged
together
evaluation of
teamwork (division of labor communication)
- Communication was tricky but all members were kept productive
most of the time.
do differently?
corrective actions?
- It might have been better to split the work load by section
rather then task. That way each member learned more in the lab
and also cuts the amount of necessary communication which could speed
up the production.
Template
SLG 1/13/05 at http://pr.erau.edu/~gerharts/SE300/Labs/lab1-legacy.html