project management with conventional plan-based approaches

1. Compare and contrast the Scrum approach to project management with conventional plan-based approaches, as discussed in Chapter 23. The comparisons should be based on the effectiveness of each approach for planning the allocation of people to projects, estimating the cost of projects, maintaining team cohesion, and managing changes in project team membership. (20 points) 2. It has been suggested that one of the problems of having a user closely involved with a software development team is that they ‘go native’; that is, they adopt the outlook of the development team and lose sight of the needs of their user colleagues. Suggest one way how you might avoid this problem and discuss an advantage and a disadvantage of this approach. (20 points) 3.  To reduce costs and the environmental impact of commuting, your company decides to close a number of offices and to provide support for staff to work from home. However, the senior management who introduce the policy are unaware that software is developed using agile methods, which rely on close team working and pair programming. Discuss a problem that this new policy might cause and how you might get around it. (20 points) 4.  Explain how the principles underlying agile methods lead to the accelerated development and deployment of software. (20 points) 5.  Explain why the rapid delivery and deployment of new systems is often more important to businesses than the detailed functionality of these systems. (20 points)