Team Name: Sagres

Date

Progress

Comments/Risks

02/04/08

 

Proposal: Finished with operations, problem definition and planning proposal last semester.  Design proposal out for review.

SOW: Signed

SRS: High-level complete. Refining this semester.

Architectural documents:

Process definition: ACDM

Reflection: Will probably skip doing QAW because customer doesn¡¦t know enough

Others:

-          Iteration plan complete incl. exit criteria

-          Client does not have two of the systems team (out of four) for which the system should be designed to operate with

 

 

 

 

Team Name: Korea Team 1 SK Telecom Project

Date

Progress

Comments/Risks

02/04/08

 

Proposal:

SOW:

SRS:

Architectural documents:

Process definition: 

Reflection:

Others:

-          Worked with client to renegotiated schedule/scope because of lost team members.  Customer was understanding.

-          Specifically got more time for arch. documentation and delayed detailed design docs and demo

 

 

 

Team Name: Korea Team2 AOB

Date

Progress

Comments/Risks

02/04/08

 

Proposal: Updating operations, design, and planning proposals for ACDM.

SOW: Signed

SRS:

Architectural documents:

Process definition: ACDM

Reflection: Need better risk management (top 5 risks identified last semester, but not mitigated or monitored)

Others:

-          Pushed by Korean mentors to reduce size of status meeting agenda and meeting (ideally down to 1 pg).  Mentors here recommend less dense info.  Working to find balance.

-          Working to define granularity of tasks and goals for this semester

-          Documentation of legacy system (esp. arch) is incorrect

 

 

 

 

 

Team Name: Alchemy (MDM-CAP)

Date

Progress

Comments/Risks

02/04/08

 

Proposal: Finish design and implementation proposal this semester

SOW: Signed

SRS: Rqmt¡¦s and QA scenarios to be updated from QAW

Architectural documents: Working on notional arc

Process definition: AUP/ACDM

Reflection: QAW was very useful

Others:

-          Still struggling with planning and task granularity

-           

 

 

 

Team Name: Buzzers (Bosch)

Date

Progress

Comments/Risks

02/04/08

 

Proposal: Finished planning, problem definition and operations proposal. Update Problem definition and planning proposal

SOW: Signed

SRS:

Architectural documents:

Process definition: ACDM

Reflection:

Others:

-          Prototyping for pieces of high-level reqm¡¦ts, including integrated UI.  Review with client is positive and expects some good design ¡§innovations.¡¨

-          Working with Dr. Herbsleb for extra suggestions

-           

 

 

 

Team Name: Pangea (SCS)

Date

Progress

Comments/Risks

02/04/08

 

Proposal: Operation, planning, problem definition proposal finished

SOW: Signed

SRS:

Architectural documents: Notional in progress

Process definition: AUP + ACDM

Reflection:

Others:

-          Held use case workshop for remaining use cases

-          Have notional arch., but needs more work to improve different perspectives

-          Planned SRE next week, hope to do QAW (but haven¡¦t found anyone to facilitate yet)

 

 

 

Team Name: Lingua Franca (SEI )

Date

Progress

Comments/Risks

02/04/08

 

Proposal: Planning, operations, and problem def complete. Updating design and implementation proposals

SOW: Should be signed this week, lead client on travel

SRS: Includes arch drivers, working to refine details before going beyond notional arch

Architectural documents:

Process definition:

Reflection:

Others:

-          Working with Rita to understand use of project for planning

-          Planning to conduct SRE in next few weeks