There has been a rapidly rising interest in these new approaches to software development such as Extreme Programming, Scrum, Adaptive Software Development, Feature-Driven Development, and Dynamic Systems Development Methodology. Furthermore, scores of organizations have developed their own “lighter” approach to building software.

This tutorial is based on the material in Jim Highsmith’s book, Agile Software Development Ecosystems. He is the developer of one of the Agile Methodologies (Adaptive Software Development), a coauthor of the Manifesto for Agile Software Development, and founding member of the AgileAlliance. The workshop addresses key questions: What are Agile Methodologies? What problem domains to Agile Methodologies address? What are the common principles and practices of the various Agile Methodologies? What are the similarities and differences between the various Agile Methodologies?

We have identified enough principles, patterns, and practices to provide our craft with a solid definition. This definition gives us something we may not have had before -- pride in workmanship. For though we may have been able to take pride in some of our projects before, we weren't often able to take pride in the “way” those projects were build. Now, we can take pride in ”how” we build software, not just in the software we build.

This tutorial is mapped to the International Association of Facilitators’ schema for effective meeting management. The instructors teach with a high-energy and highly interactive style, maximizing the learner’s experience through the application of sound adult learning techniques. Templates and agenda guides will be provided as “take-aways.”

Better, cheaper, faster software development. You can have all three—if you adopt the same “lean” principles that have already revolutionized manufacturing, logistics and product development.

• Iterating towards excellence: software development as an exercise in discovery
• Managing uncertainty: “decide as late as possible” by building change into the system
• Compressing the value stream: rapid development, feedback, and improvement
• Empowering teams and individuals without compromising coordination
• Software with integrity: promoting coherence, usability, fitness, maintainability, and adaptability
• How to “see the whole”—even when your developers are scattered across multiple locations and contractors

Simply put, Lean Software Development helps you refocus development on value, flow, and people—so you can achieve breakthrough quality, savings, speed, and business alignment. For an outline of the tutorial, go to:  http://www.leantoolkit.com/leantutorial.htm

Short lectures will explain just enough of Extreme Programming to establish the context for test-driven design. These will be followed by live demonstrations and laboratory exercises. The labs will use simple Java, but the emphasis is on familiarity with the frameworks, tools and techniques, not programming. If you are unfamiliar with Java you will learn enough just by watching so as to be able to complete some of the exercises and received all of the benefits of the class.

Bring a laptop, or join someone who has, to do hands-on exercises. Bring a wireless networking card to participate in additional "online" activities. Install java at home to save time in class. Google "sun java download" to find a version for your computer.

1. An understanding of empirical processes, emergence, self-organization, and adaptation;
2. A detailed understanding of Scrum principles, flow, roles, artifacts, and operation;
3. A detailed case study of Scrum being used to solve a competitive problem for a large financial institution;
4. A detailed description of the role and responsibilities of the product owner, ScrumMaster, and development team;
5. A description of how to use Scrum to develop software for mission critical and life critical systems;
6. An approach to using Scrum for fixed price/fixed date contracts;
7. An understanding of how Scrum addresses CMM level 2 and 3 requirements;
8. An understanding of how to quickly implement agile software development so projects start producing product increments;
9. An understanding of implementation alternatives and their benefits for Scrum;
10. An understanding of how Scrum solves predictability and productivity issues for projects and products;
11. An understanding of the overlap between Scrum and Extreme Programming and how to use Scrum to wrap Extreme Programming to provide project and organizational scalability and control; and,
12. An understanding of Scrum as a methodology and toolset that can be used to Plan, Customize, and Manage any type of project.

www.lindarising.org

A Crystal methodology aspires to be the least constrictive and yet effective methodology for any particular project team. This tutorial describes the principles and techniques for shaping a methodology to the project-team combination, introduces the colors in the Crystal family, compares different examples of the Crystal family to each other relative to the principles, and shows the differences between Crystal Clear and XP. Expect to learn the methodology tuning principles, and experience how easy and fruitful a methodology-tuning session can be.