This page is for the work on Chapter 13: Managing Changes.

Owners of this page, please introduce yourself:

Name/ID	Name a hobby or Something that you like to do:	Say something about your experience with software	What would you like to learn from this course?	How would you like to learn from this course?
Md.AliullahBhuiyan 093-25-138	Browsing Internet,Reading Book and Watching English Movie.	Few month ago i completed a software for a company.The name of software was Stock Control Management.	We can learn from this course,how to complete a software properly with low cost within short time.Also included reliability and extra features.	By wiki our all of works we can do/share easily.For that, we can share previous experiences and can provide new idea for the new challenging projects.Using Paper we can collect new information which will effective to do a project works and helpful for analysis about different projects.
Md.Azaharul Haque Biswas/ID:102-25-167	Traveling, Play with Computer, Watching different type of Movies	Client/End user is very much important issue for customized software	How can I manage different type of projects?	If we discuss with more scenarios and read less then we can.

EDITED BY: Md. Aliullah Bhuiyan. >>ID: 093-25-138<<

Md. Azaharul Haque Biswas.>>ID:102-25-167

Task 1: Summaries the chapter below in terms of bullets: (10 marks)

Chapter 13

Managing Changes to the software Project

=============================================================================

Bullets are-------

1. Planning for and managing project changes.

2. Controlling Process group.

• Scope
• Schedules
• Costs
• Risks
• Communication
• Team member performance
• Contract administration
• Quality

3. Creating and following a change control system.

• Determining the value of the proposed change.
• Correcting mistakes

4. Getting a handle on project costs.

• Controlling Project Costs
• Managing project cost variances
• Estimating the cost of change

5. Dealing with variances in a schedule.

• Controlling the Project Schedule

• Managing project time variances

• Variance analysis:

• Estimating impact of change on the project schedule

• Forecasting schedule variances

6. Expecting and accepting changes.

Description of Bullets are:

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
1. Planning for and managing project changes:

Plan for changes. That’s right; you will encounter changes during your software project, so accept these facts, and just plan for them Encountering changes during your software project is not a sign that you planned poorly; it’s a sign that you are living in the real world where people change their minds, risks are encountered, and stuff happens. You’re better off accepting the fact that you will encounter changes so that you can plan accordingly.

2. Controlling Process Group:

The controlling process group is concerned with monitoring and controlling the following factors:

1. Scope.

2. Schedules.

3. Costs.

4. Risks.

5. Communication.

6. Team member performance.

7. Contract administration.

8. Quality.

3. Creating and following a change control system:

You must create an effective change control system because changes are inevitable and even at times necessary. One way to prepare for these changes is to create and follow an effective change control system.

Determining the value of the proposed change:

When project changes are proposed, you need to determine the cost of implementing the change, as well as the value that the proposed change will add to the project.

Correcting mistakes:

At times, you’ll be required to make project changes in order to correct mistakes either in coding or software testing or because of misunderstandings, miscommunications, or any number of other reasons. If you have the appropriate change control system in place and you complete the appropriate project planning processes, making corrections is a more manageable.

4. Getting a handle on project costs:
Controlling Project Costs:

Earlier in this chapter, we mention the Project Management Institute (PM)project management process groups. The project management process group that is concerned

with controlling project scope, costs, schedule, quality, and risks is the controlling process group.

Managing project cost variances:

During the planning phase of your software project, you gather information you need to create your cost estimates, budgets, and baselines.Chances are that with a software

project, most of your costs will be associated with resources required to complete the project, including programmers,analysts, software engineers, application testers, and

other personnel.Throughout the project, you need to be aware of variances in what you

planned for your project to cost, compared to actual costs

Estimating the cost of change:

When you estimate the cost of a change, you should consider not just the part of the

project that you’re changing, but also other affects of this change.During the planning

phase of your software project, when you create your cost management plan, you

identify the methods you might use to identify cost changes int he project.

Forecasting variance:

Forecasting variance can be useful for several reasons, but the most important is that

your stakeholders will expect this information from you and you will want to know whether and when you need to take corrective action to bring your project costs back in line.

5. Dealing with variances in your schedule:

Controlling the Project Schedule:

When creating the project schedule during the planning phase of your software

project, you probably spent a large portion of your time gathering information.

You probably did most or all of the following:

1. Spoke to project managers who had managed similar projects.

2. Gathered requirements from appropriate stakeholders and worked with

them and your project team to prioritize and sequence the tasks.

3. Built the schedule from the ground up focusing on each of the project

activities, their definition, their sequencing, and estimating their durations.

4. Considered the appropriate resources required to complete the project successfully

in the desired time frame.

6. Created a schedule management plan that defined how you would control

the project schedule and manage project time variances.

Managing project time variances:

You created an extremely thorough work breakdown structure (WBS), you spoke to the appropriate people to gather their insight and wisdom, you spent a suitable amount of time gathering requirements,and you created your project network diagram use to manage and monitor schedule variances.

Variance analysis:

Use this to determine whether where you planned to be in the schedule is the same as where you really are in the schedule. This will also help you in determine what (if any) corrective action to take. This is not an exhaustive list of all the tools and techniques that could possibly help you in managing schedule variances and controlling your schedule. This is just a list to get you started and point you in the direction of knowing that there are ways to monitor your schedule; you need to decide which methods are right for your project.

Estimating impact of change on the project schedule:

When a stakeholder submits a change request using the change control system that you defined and communicated, you will need to determine the impact of the potential change. The requested change may impact the project costs, schedule, and/or scope, but for the benefit of this section we are just focusing on the impact to the project schedule.

.
Forecasting schedule variances:

Forecasting schedule variances enables you to look ahead to determine whether you’re on schedule. Having this knowledge provides you with an opportunity to show your creative talents and start defining corrective action to bring the project schedule back in line with your plan.

6. Expecting and accepting changes:

No matter how diligently you gathered stakeholder requirements and how detailed your project plan is, you will, at some point(s) in your software project, experience a need for project changes, Changes are to be expected; that’s why you have risk management and

communication plans and change control. In software projects,changes can mushroom into expensive, time munching beasts, but with the proper planning, change control processes,

and expectation setting, you can manage the changes.

===============================================================================

=============================================================================

Task 2: Explain the bullets in terms of the Grameen Bank Form 15 system.

(10 marks).

EDITED BY: Md. Aliullah Bhuiyan. >>ID: 093-25-138<<

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Group-3 : Desktop Based

Fig 03: Estimation for Grameen Bank [GB] by Desktop.

From the above figure 3 we want to say that for better solution by desktop we need to divide the HeadOffice of GrameenBank in 6 zones [Where Head Office= 6 Zone][1 zone = 13 areas] and [1 area=8 branches].

1. For each zone we need 4 PCs. So, 4 * 6 = 24 PCs
2. For Scanning we need one scanner.
3. Others maintenance cost and manpower is required for the whole task.
4. By the above details you can see we need only 24 pcs]
5. From Head Office the inputted data will be sent to all branches by Print copy,.

Structure of cost on Desktop Based Procedure.
Head office total cost =1,030,000TK[Our best choice]
Zonal office total cost = 8,95,000TK.
Area office total cost = 6,010,000TK.
Branch office total cost = 24,005,000TK.

Managing Changes to the software Projects according to the above details we have to follow the steps those are given below:

• Schedules.
• Costs.
• Risks.
• Communication.
• Team member performance.
• Product Quality.
• Determining the value of the proposed change.
• Correcting mistakes.
• Controlling Project Costs.
• Managing project cost variances.
• Estimating the cost of change.
• Controlling the Project Schedule.
• Managing project time variances.

• Estimating impact of change on the project schedule.

• Forecasting schedule variances.