Make your own free website on Tripod.com

Capstone Roadmap

Project Guidelines- Fall 2005

Home
FAQ's
Contact

Introduction

 

Starting from Fall 2005, we will unleash a new version of the capstone course experience  that is more adaptive , more  team-intensive and more speedy . This version is a response to our evolutionary capstone experience in real world projects in which change management , effective collaboration and agility  have been  dominant factors in influencing  team performance and problem solving quality  . Our approach benefits tremendously from agile software development strategies with more emphasis on Scrum and FDD (feature-driven development) as key models   .

FDD-SCRUM Presentation

SCRUM Development Process

FDD Process Diagram

FDD Process Explained

UML Use Case , Class and Sequence Diagrams

UML Tutorial 1

UML Tutorial 2

Timeline

 

      As a result and based on the fact that the deadline for forming all teams and selecting all projects will be Monday   19th  , 2005 , the following is an illustration of how all projects will progress    :

 

1-      Each team will have to finish their project within a series of (5) sprints (or iterations) where each sprint is two-week long as follows   .

 

a.      Sprint (1)  starts on Monday Sep 26th and  concludes on Monday Oct 10th . The deliverables should be presented to the client during that week . A presentation to the class is also required on Tuesday Oct 11th or Wednesday Oct 12th depending on your section time  

b.      Sprint (2) starts on Monday Oct 10th and concludes on Monday Oct 24th .The deliverables should be presented to the client during that week. A presentation to the class is also required on Tuesday Oct 25th or Wednesday Oct 26th depending on your section time 

c.       Sprint (3)  starts on Monday October 24th and  concludes on Monday Nov 7th . The deliverables should be presented to the client during that week. No presentation is required to the class for this sprint

d.       Sprint (4)  starts on Monday Nov 7th and  concludes on Monday Nov 21st . The deliverables should be presented to the client during that week. No presentation is required to the class for this sprint.

e.       Sprint (5)  [FINAL ONE] starts on Monday Nov 21st and  concludes  on Monday Dec 5th . The deliverables should be presented to  both the client and the class in the classroom . Depending whether you are in a Tuesday or Wednesday capstone section , your FINAL PRESENTATION  will be either on Tuesday Dec 6th or Wednesday Dec 7th .

 

2-      Development teams meet with the client, or product owner, before each sprint to prioritize the work to be done and select the  tasks the team can complete in the upcoming sprint.

3-      During each sprint, the ideal situation is that the team stays on track by holding brief 30-minute daily meetings possible . If that was difficult, the team should have at least three brief 45-minute meetings each week.  

4-      At the end of each sprint, the team delivers a potentially shippable product increment.

Deliverables

 

The FDD methodology mandates five phases  :

 

1- Develop an Overall Model

2- Build a Features List

3- Plan by Feature

4- Design by Feature

5- Build by Feature

 

Sprint number

Starting Date

Ending Date

Client Presentation

Class Presentation

FDD Phase

Deliverables

Key Roles

Sprint 1

 

(2 weeks)

Sep 26th

Oct 10th

Required

 

 

- Oct 11th       

 - Oct 12th

 

Present and deliver Sprint 1  in class

 

Progress report required

-Entry criteria

-Overall Model

-Feature List

-verification

-exist criteria 

-Requirements analysis document

- features list

- Class Diagram

- Sequence Diagram

-Compliance with entry/exit criteria

-Project manager

-Chief Architect

-Modeling Team

- Features list team

-Chief Prog.

-Domain Expert

 

Sprint 2

 

(2 weeks)

Oct 10th

Oct 24th

Required

- Oct 25th        

- Oct 26th

 

Present and deliver Sprint 2 in class

 

Progress report required

-Entry criteria

-Plan by Feature

-Design by Feature

-Build by Feature

-verification

-exist criteria 

First features set :

 

 -Plan document

-Design  document

- Features set prototype 

-Compliance with entry/exit criteria

-Project manager

-Chief Architect

- Chief Prog.

- Features sub-groups

 

Sprint 3

 

(2 weeks)

Oct 24th

Nov 7th

Required

No  class presentation

or deliverables required

 

Progress report required

-Entry criteria

-Plan by Feature

-Design by Feature

-Build by Feature

-verification

-exist criteria 

Second features set :

 

 -Plan document

-Design  document

- Features set prototype 

-Compliance with entry/exit criteria

-Project manager

-Chief Architect

- Chief Prog.

- Features sub-groups

 

Sprint 4

 

(2 weeks)

Nov 7th

Nov 21st

Required

No  class presentation

or deliverables required

 

Progress report required

-Entry criteria

-Plan by Feature

-Design by Feature

-Build by Feature

-verification

-exist criteria 

Third features set :

 

 -Plan document

-Design  document

- Features set prototype 

-Compliance with entry/exit criteria

-Project manager

-Chief Architect

- Chief Prog.

- Features sub-groups

 

Sprint 5

 

(2 weeks)

Nov 21st

Dec 5th

Combined with class presentation

- Dec 6th   

- Dec 7th

 

Present and deliver all sprints from

 1-5   in class

 

Final Progress report required

-Entry criteria

-Plan by Feature

-Design by Feature

-Build by Feature

-verification

-exist criteria 

Forth and  combined features sets :

 

 -Plan document

-Design  document

- Features set prototype 

-Compliance with entry/exit criteria

-Project manager

-Chief Architect

- Chief Prog.

- Features sub-groups

 

4-   Key Definitions

 

-          Sprints : Time boxed two-week iterations .The team can reduce delivered functionality during the sprint but the delivery date cannot change .

-           Feature : client-valued function that can be implemented in two weeks or less .They usually refer to user-interface features . Features are grouped into feature Sets which represent a logical grouping of features that could be delivered to a user as a component in a short time frame.