Question 2:Based on the phases discussed in the case study please give a list of stages we

should follow for the complete lifecycle of a project.

Answer:

The list of stages to be followed are:

1.Requirement and analysis

2.Design

3.Coding

4.Customer Communication /Change Request Management

4.Testing

5.Maintenance

Question3: Create a rough process map for the Testing stage of the project.

Answer:

The following stages comes under as a testing stage of the project

  1. Requirements Analysis: Testing should begin in the requirements phase of the software development life cycle(SDLC).
  2. Design Analysis: During the design phase, testers work with developers in determining what aspects of a design are testable and under what parameter those testers work.
  3. Test Planning: Test Strategy, Test Plans,
  4. Test Development: Test Procedures, Test Scenarios, Test Cases, Test Scripts to use in testing software.
  5. Test Execution: Testers execute the software based on the plans and tests and report any errors/bug found to the development team.
  6. Test Reporting: Once testing is completed, testers generate metrics and make final reports on their test effort and whether or not the software tested is ready for release.
  7. Retesting the Defects

Question4: Prepare the Minutes of meeting for Kumar’s meet with Narendra, Zaheer & George.

Answer:

Project Name

Venue

/ Fact-Tree Global Services.
Attendees / Kumar / Zaheer
Narendra / George
Minutes by / Kumar
Agenda
Different ways to spend time executing a typical project.
Experience of the First week/month after moving from a small company.
Does all these software process, so many in number, allow you to be
innovative at work?
Challenges faced to get information from onsite.
Culture related problems.
How much percentage of process is actually followed in process oriented company.
Benefites of the process.

Summary of Discussion

  1. The maximum time spent is on Requirement analysis while executing a project.

  1. Transition from a smaller company to a process oriented company is not very difficult but it takes time to adjust.

  1. If the scheduling of processes is done properly process allows one to be innovative.

  1. Onsite challenges are mainly people oriented.

  1. Managers decide which processes of client to be adapted, tailored or rejected according to the project.

  1. The degree to which processes are used depend on time, cost, resources, customer support and flexibility.

  1. Processes ensure proper documentation, which in turn helps to analyze the root cause of the problem if things go wrong.

  1. Processes quantify knowledge and make it available for future.

  1. It ensures uniform understanding of customers needs by the team members in larger teams

Discussions:

1. We see both optimistic and pessimistic views about processes. Whom do you find

more persuasive? How might these two views be reconciled?

Answer: According to the case study if we follow the processes then the development process becomes more systematic and everything gets documented and it becomes easy to track any problem. But following the process is more time consuming and lengthy process. Although following the process has some negative points but it is always necessary to follow the processes in a project. If the processes are followed in a project then it becomes very easy to track all the requirements of the customer and if any of the changes comes at later stage from the client it becomes easy to estimate the required changes in existing code and even if some persons leave the project, the project does not come to a halt. The new persons can take it over very easily.

Following the processes is more persuasive.

Reconciliation of two views:

The processes are having some pros and cons. But it is not necessary that one should follow all the steps blindly. The processes can be tailored or changed according to the project requirement. According to project requirement any approaches like waterfall or iterative approaches can be followed. So before starting any processes first the feasibility and usefulness should be seen and wherever necessary one can tailor the process according to requirement but even if the process is tailored it should be documented, so that other person can also understand that why you are not following the standard processes.

2. Based on the data provided in the case study it looks like processes are everything.

Bring out the criticisms of having processes. Given the criticisms of processes, why

are they still indispensable?

Answer:

Criticism of having processes:

  1. It is more time consuming.
  2. Processes make you more bound and channel your thought processes.
  3. Managing resources becomes more critical.
  4. Processes dictates you how to do anything and if followed blindly it stops innovations.
  5. Most of the time you are doing documentation.

Although there are some drawbacks but still it is indispensable.

  1. Processes ensure proper documentation, which in turn helps to analyze the root cause of the problem if things go wrong. Also it makes easier to explain to the customers about what went wrong
  2. Processes quantify knowledge and make it available for future.
  3. It ensures uniform understanding of customers needs by the team members in larger teams where there are many project leaders, approval becomes a problem. It is difficult to understand if the customer needs are being understood in a similar fashion.

3. Which of the process-centric or product-centric view will help you in doing your

academic projects? What kind of projects do you think will be benefited most by

being process centric? What kind of projects get support from product centric view?

Answer: Product-centric view will help in developing academic projects, because in academic projects the requirements are more or less stable and most of the time team size is very- very small maximum 4 persons. And there are no managers or no client discussions in academic projects. But some documentation is needed to understand the project.

Process centric: Large and long term projects need process centric approach, where requirements are not stable and it keeps on changing and a well defined hierarchy exist in the company. Client discussions are there, the team keeps on changing. Some old people are leaving the project and some new persons keeps on joining the project.

Product centric approach: Very small projects need product centric approach. If 4-5 persons are handling the project and they are not going to leave till the end of the project. The requirements are crystal clear and they are not going to change.

Pinki ye kuchh sites hain ek baar open karke dekh lo....achhi hain......


/