Notes

3.1. At the end of their study program, students in a software engineering course are typically expected to complete a major project. Explain how the agile methodology may be very useful for the students to use in this case. 3.2. Explain how the principles underlying agile methods lead to the accelerated development and deployment of software. 3.3. Extreme programming expresses user requirements as stories, with each story written on a card. Discuss the advantages and disadvantages of this approach to requirements description. 3.4. In test-first development, tests are written before the code. Explain how the test suite may compromise the quality of the software system being developed. 3.5. Suggest four reasons why the productivity rate of programmers working as a pair might be more than half that of two programmers working individually. 3.6. Compare and contrast the Scrum approach to project management with conventional plan- based approaches as discussed in Chapter 23. Your comparison 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. 3.7. 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 Scrum. Explain how you could use technology to support Scrum in a distributed environment to make this possible. What problems are you likely to encounter using this approach? 3.8. Why is it necessary to introduce some methods and documentation from plan-based approaches when scaling agile methods to larger projects that are developed by distributed development teams? 3.9. Explain why agile methods may not work well in organizations that have teams with a wide range of skills and abilities and well-established processes. 3.10. 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 three ways how you might avoid this problem, and discuss the advantages and disadvantages of each approach.