1. Projects, Assignments, and other Assessments

2. Which of the following are Agile Programming approaches?
Advanced System Prototyping XP XT
Adaptive Software Development
Huddle
Scrum

3. As groups, develop examples of software development
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
When might the other be valuable? Why?
Which do you prefer? Why?
How would you explain these in your own words?
For each of the values, provide at least one example illustrating it.

4. As a team, put the 13 principles in order by priority
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Welcome changing requirements, even late in development
Deliver working software frequently
Businesspeople and developers must work together daily throughout the project
Build projects around motivated individuals. Given the environment and support they need, and trust them to get the job done.
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation
Working software is the primary measure of progress
Agile processes promote sustainable development
The sponsors, developers, and users should be able to maintain a constant pace indefinitely (Not in all lists)
Continuous attention to technical excellence and good design enhances agility
Simplicity – the art of maximizing the amount of work not done – is essential
The best architectures, requirements, and designs emerge from self organizing teams
At regular intervals, the team reflects on how to become more effective, then tunes and adjust its behavior accordingly.
Can you discard one?
If you were going to add a principle, what would it be?

5. As a team, list the five most important reasons to use agile methods

6. As a team, list the five most important reasons NOT to use agile methods

7. Ａｄｏｐｔｉｏｎ Ａｓｓｅｓｓｍｅｎｔ Ｍａｔｒｉｘ
Ａｄｏｐｔｉｏｎ　Ａｓｓｅｓｓｍｅｎｔ　Ｍａｔｒｉｘ
Ｗｅｉｇｈｔ
Ｒａｎｋ
Ｒｅｓｕｌｔ
Duration of the project
Acceptance of change
Criticality of project
Team size
Skill level of team
Location of customer
Customer involvement
Organizational and reporting structure
Process
Documentation requirements
Layout of workplace
As a team, fill in the adoption assessment matrix. What weight (1-5) do you give each factor? For a specific project, what rank would you assess?

8. A Class Project: Putting the Agile principles and practices in context
Consider the Agile Manifesto, principles and practices.
What are the Disciplined principles and practices?
How do you personally weight these items?
How do you think companies weight them?
Consider three groups: developers, companies, and users. Why would these principles or practices be important to them? What do they want?

9. As a team, discuss how the agile values and practices help with these problems
Requirements are not clearly communicated
Requirements do not solve the business problem
Requirements change prior to the completion of the project
Software (code) has not been tested
Software has not been tested as the user will use it
Software developed so that it is difficult to modify
Software used for functions for which it was not intended
Projects not staffed with resources required
Schedule and scope commitments made before understanding requirements or technical risks
Lindstrom and Jeffries (2004)

10. Paper Write a paper examining Reasons projects fail
How agile development addresses this
Other benefits and drawbacks to using agile development

11. Project
Develop a plan for introducing agile development methods in an industrial setting
Include publicity, training, changes in organizational processes and procedures, and any other impacts
Provide a business case supporting this change

12. Project
Design a research plan to investigate some aspect of agile development
What is your hypothesis?
What will you measure and how?
What do you expect to learn?
Where would you publish your results?