CSE G674/2009 Project

Project Management

Section

Presented by: Amir Aref

Adib

Main Goal for 2009 Project: The

goal for this year’s project is to

expand the code capability of SEP

2008 and adding more functionality,

and focus on a different aspect of

information about a software

engineering project.

The ChallengesHow we should start the project?

1. Time limitation

2. Different people different taste and idea

3. How we can manage the project

4. New topic and …..

what should we do as a team to facilities these difficulties?

1.Define Project

Management frame work

for our project

2.Define time frame work

3.Clear what we want and

what we should do

4.Divide whole project to

small parts

Eclipse Process Framework Project (EPF)

The Eclipse Process Framework (EPF) aims at

producing a customizable software process

engineering framework, with exemplary

process content and tools, supporting a broad

variety of project types and development

styles.

EPF Goal

By using EPF Composer you can create your

own Software development process by

structuring it in one specific way using a

predefined schema.

EPF

Project Management

After discussion with the class, we all

decided to apply Agile methodologies for

this year’s project. We believe our project

can adapt Agile/Scrum methodologies. In

result, we summarized the main concepts of

Agile methodologies that we can apply in

our project as a framework in EPF.

Scrum Overview:

Scrum is an experimental Agile project

management framework used to deliver

increments of high value to the customer

iteratively. Scrum relies on self

organizing, empowered teams to deliver

the product increments. It also relies on a

customer , or Product Owner, to provide

a team with a list of desired features using

business value as the priority mechanism.

One week or two weeks

Daily Communicatio

n

Product BacklogAs prioritized by Product Owner

Sprint Backlog

Backlog tasksexpandedby team

Weekly ScrumMeeting

Potentially ShippableProduct Increment

General role for team

Each team does not include any of the

traditional software engineering roles such as

programmer, designer, tester, or architect.

Everyone on the project works together to

complete the set of work they have

collectively committed to complete within a

sprint. Scrum teams develop a deep form of

camaraderie and a feeling that "we're all in this

together."

Each member was responsible to complete all the

assignments that were assigned to him/her in

each sprint.

Some of the principles behind the Agile

Manifesto are:

1. Customer satisfaction by rapid, continuous

delivery

2. Working software is delivered frequently

3. Working software is the principal measure of

progress

4. Even late changes in requirements are

welcomed

5. Close, cooperation between all members

6. Face-to-face conversation is the best

7. Projects are built around motivated individuals,

who should be trusted

8. Simplicity

9. Self-organizing teams

10.Regular adaptation to changing circumstances

No Change!•We are already running late. •I need to meet my date.•We worked hard to prevent change at the start.

Cos

t of

cha

nge

Promised date

The following terminology is used in Scrum:

Roles

Product Owner /PM:

The person responsible for maintaining the Product Backlog by

representing the interests of the customer.

ScrumMaster/ Leader :

The person responsible for the Scrum process, making sure it is used

correctly

and maximizes its benefits.

Team :

A cross-functional group of people responsible for managing itself

to develop the product.

Scrum Team Product Owner, ScrumMaster and Team

Artifacts

•Sprint burn down chart

weekly progress for a Sprint over the sprint's

length.

•Product backlog

A prioritized list of high level requirements.

•Sprint backlog

A list of tasks to be completed during the

sprint.

Research On Previous project

Research on new topic

Find out any possible

extensions and

improvements

Work on UMLWorking on development

Working on Requirements

and documentation

Integration

Project Schedule

2/25: By this date all groups should have clear idea

(extensions) and interfaces with other groups. they

should working on their extensions and interfaces.

At least 50% of their works should be finished at this

point.

3/30: All design (extensions)should be complete by

this point and all tools should successfully be

integrated . (Our goal is to be done with everything

by this date)

3/31: Final testing and finalize documentation begin

4/13: End of Class! Final presentation, all

deliverables.

Say goodbye, have fun for summer break:)

If the decision were solely up to you, would you continue using Scrum?

Red YellowGreenBlueRedBlue

YellowGreenBlue

0%

10%20%

30%40%

50%

60%70%

80%90%

100%

No Yes

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

No Yes

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

No Yes0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

No Yes

94% Yes80% Yes

82% Yes88% Yes

India

OverallEurope

Source : www.bcic.org.in/notifications/BCIC-BSPIN/Mr.SahardSharma,Yahoo.ppt

US

Yahoo survey

Advise to Next Group:

•Extend EPF and link it with your

project.

•Review our final Specification

•Review Our task board, It will

provide list of tasks and estimation

on each task (time frame work)

•Review sprint backlog of each team.

You can find out more information at:

http://www.scrumalliance.org/

Book “Agile Software Development with

SCRUM” by Ken Schwaber, Mike Beedle

Book “Agile Project Management with

SCRUM” by Ken Schwaber

http://www.controlchaos.com/ - Ken

Schwaber’s own site

Scrum for Managers

http://mitchlacey.com/docs/

scrumformanagers.pdfSource : xpday5.xpday.org/slides/59-minuteScrumXPDay5.ppt

THANK YOU !