Team Assignment 4

Star day:16/2/2012

End day:25/2/2012

MembersName ID

Lê Ba Dung- Leader T09

Đăng Thê Cương T09

Đô Tiên Hưng T09

Nguyên Ngoc Ngân T096357

Nguyên Trong Nghia T09

Nguyên Quôc Trung T09

TEAM

2

Question• A paper (≤ 2 pages) briefly describing how a software development methodology impacts the team’s GQM definitions. • Reporting of actual individual effort log data to Director by team, along with brief analysis

Answer

1. COMPARE TWO METHODOLOGIES: TRADITIONAL VS AGILE

2. COMPARE MEASUREMENT IN TWO METHODOLOGIES: TRADITIONAL VS AGILE

3. SOFTWARE DEVELOPMENT METHODOLOGY IMPACTS THE TEAM’S GQM DEFINITIONS.

1. COMPARE TWO METHODOLOGIES: TRADITIONAL VS AGILE

Traditional Agile Assume that requirements can

be known at the start of the project Product Owner/User

involvement with development team is minimal after requirements are approved

Schedule, budget, architecture and design for entire project can be created “up front” given requirements

Change managed formally. Rework is bad

Lots of documentation At the end project, Customer

will be see product following their requirement.

Assume that requirements will emerge

  Product Owner/User works

closely with development team on a daily basis

Schedule, budget, architecture and design for project evolve as requirements emerge

Change is managed informally, Rework (refactoring) is good

A few Document Product built so you always

have a working system and can “release” at any time. 

2. COMPARE MEASUREMENT IN TWO METHODOLOGIES: TRADITIONAL VS AGILE

Issue Traditional AgileRequirement

Be Care of Requirement Phase

Be Care Customer Acceptance after each sprint

Schedule Big plan up front & earned value

Velocity & Burn Down Charts

Cost Big plan up front & earned value

Developers are assigned 100% to project, so project cost is # of developers sprints

Product Change

Needs to be managed carefully

Natural part of meeting customer needs. Only need to measure # of stories

Rework & Refactoring

Rework is bad; should be eliminated

Refactoring is a natural part of meeting customer needs. No need to measure

Quality Be Care Process & product quality

Emphasis on product quality

3. SOFTWARE DEVELOPMENT METHODOLOGY IMPACTS THE TEAM’S GQM DEFINITIONS.

Traditional Agile

 Schedule

Description In traditional, Schedule will be upfront and we will consider actual schedule in schedule Plan.

Schedule following user stories, when customer gives more stories, then Schedule will longer. They’re proportional.

Goal Measurement

Big plan up front & earned value

Burn Down Charts

Question - How much Budgeted Cost of Work Scheduled is there?

- How much Budgeted Cost of Work Performance is there?

- How much is the estimate schedule of each sprint?

- How much is the actual schedule of each sprint? What is the estimated versus the actual schedule for each release?

Metric - Schedule VarianceSPI

Schedule Variance in each sprint

3. SOFTWARE DEVELOPMENT METHODOLOGY IMPACTS THE TEAM’S GQM DEFINITIONS.

Cost

   

Description

Scope (requirements - features) is well understood and can be fully defined at the start of a project. Therefore, we measure cost for all activities in traditional project.

In Agile project, we start the project by ambiguous scope. So members have to discover requirements throughout the project. Therefore, we cannot understand fully activity in the agile project. We can only measure based on features that we understand in agile project.

Goal Measurement

Big plan up front & earned value

Burn up Charts

Question - How much is the estimate cost of each activity?

- How much is the estimate cost of each release?

- How much is the actual cost for each activity?

- How much is the actual cost of each release?

- What is the estimated versus the actual cost for each activity? 

- How much is the estimate cost of each sprint?

- How much is the actual cost of each sprint?

- How much is the budget planned of the release?

- How much is the actual cost of the release?What is the estimated versus the actual cost for each release?

Metric - Cost VarianceCPI

- Cost Variance in each sprint.- Cost Variance in each

release. 

3. SOFTWARE DEVELOPMENT METHODOLOGY IMPACTS THE TEAM’S GQM DEFINITIONS.

Requirement

   

Explain In traditional natural, Requirement is the first phase in life cycle, and output of this phase is input of that phase, if this phase is not clearly, you will spend expensive cost to rework. So Requirement phase very important and be carefully.

Agile only base on stories of customer and do product in sprint and consider with customer. Agile is not care requirement clearly.

Goal Measurement

Managing requirement clearlyFeedback customer after Each sprint

Question

- How many requirements is the project?

- How many requirement is the project‘s customer acceptance.

- How many requirements change is the project? Frequency of each change?

- How many requirements are there traced?

- How many Stories acceptant are there in project?How many Stories are there in project?

Metric - % requirements change.- % requirements acceptance of

customer.- # Change of each requirement

change.% number Requirements traced.

% stories acceptant of customer.

  

Thank you for listening

Team

Team Assignment 4