program selection system

Utilizing pair programming in the classroom requires specific classroom management techniques. We have created eleven guidelines for successfully implementing pair programming in the classroom. These guidelines are based on pair programming experiences spanning seven years and over one thousand students at North Carolina State University. In Fall 2007, pair programming was adopted in the undergraduate human-computer interaction (HCI) course at Virginia Tech.

Congratulations! You’ve just been granted initial funding for your Agile project! As the product manager you understand the market opportunity for your new Beer Miles rewards loyalty program, but how do you go from the business case to a product backlog? Your accountant says return on investment is key, the Marketing Director says user experience and community are key, while the IT says scalability and fault tolerance are high priorities. You have limited time and budget, and the pressure is on to make the product a success.

What is an Agile coach? What is not agile coaching? How do I start and grow as an Agile coach? A short introduction by Erik Lundh, founder of Agile Coaches Guild, and member of a cross-disciplinary team that currently trains a significant number of agile coaches for a large international development organization.

Drawing from our experience implementing Agile not only across cultural and physical boundaries with on/off shore blended teams, but within limitations that aren’t so obvious - we play an interactive game to learn about how people from diverse groups with different learning styles can gain knowledge and insight in cooperative and competitive settings. We will draw from this workshop’s experiential learning to feed a larger discussion about intercultural work groups, whether these groups are from different countries or different work disciplines.

A Coding Dojo is a meeting where a group of programmers gets together to learn, practice, and share experiences in an inclusive and collaborative environment, while solving together a programming challenge. In this session, the presenters will share their experiences of creating and running a Coding Dojo in São Paulo, Brazil. They will present their tailored process to conduct the sessions, outline lessons learned from the weekly meetings since the first session in July, 2007 and discuss the aspects of a Coding Dojo that foster learning and tacit knowledge sharing.

A Coding Dojo is a weekly meeting where a group of programmers gets together to learn, practice, and share experiences. The session is organized around a programming challenge (Code Kata) where people are encouraged to participate and share their coding skills with the audience while solving the problem. In an inclusive and collaborative environment, the participants discuss and practice a wide range of topics, such as: TDD/BDD, Agile, refactoring, pair programming, OO, design, Algorithms, different programming languages, paradigms, and frameworks.

In this session, the presenters will share their experiences of creating and running a Coding Dojo in São Paulo, Brazil. They will present their tailored process to conduct the sessions, improved over time by retrospectives. They will also discuss the aspects of a Coding Dojo that foster learning and tacit knowledge sharing, presenting the lessons learned from the weekly meetings being held since the first session in July, 2007.

Many meeting and training sessions rely on exercises in which the group generates data, which is then reviewed to create an understanding of the possible answers to a posed question. Variations on this theme can be found in reviews of business proposals and prioritizing requirements. Thiagi (full name Sivasailam Thiagarajan) has created so called ‘frame games’ that allow an adaption to the specific needs of a situation.

In this workshop I will provide an introduction of the frame-games to the participants. We then actually run a game, to become familiar with the concept and to select the framework which we will use in the workshop. Given a reference structure which I will provide (i.e. which kind of decision will the game which we design support) I will put the group to work (and participate) in creating the game. Once done we’ll run it, to learn if the game needs tuning.

The goal of the workshop is to collect and develop useful guidelines for Agile Coaches. We encourage you to come along to share coaching experiences of what worked (or did not work) for you. You will have the opportunity to meet other practicing Agile Coaches and hearing how they work with their teams.

Background:

Relationship systems coaching is a new and emerging discipline—embodying “systemic” coaching methods—that provides Agile Coaches a new model to work with the whole system, not just individuals. By cleanly standing outside the team, we help reveal the system to itself, leading to greater team self awareness, higher cohesion and more conscious self-organization. Moving beyond the right and wrong of individual issues, we facilitate long-term persistent changes which benefit the whole system.

Most Systems Analysis and Design textbooks and courses are based on traditional (and heavy) methods, tools and processes. I encourage students to apply basic concepts to solve a business problem of their choice and customize the tools they have learned to fit their unique project. For example, all students start their modelling processes by applying the basic concepts of events and entities.

Although not a clearly defined role, we believe an Agile organization needs managers: ones with new skills, alternate mind sets, and fresh perspectives on managing. In this session we define a framework for Agile managers with eight competency areas, then springboard into a highly interactive discovery session with breakouts by competency. Participants will leave with tools and best practices they can use immediately to help the manager in their life.