Saros is an open source Eclipse plugin for distributed pair programming. It allows to do collaborative text editing with support of many participants at once. All members of a session have an identical copy of an Eclipse project and Saros keeps these copies synchronized.
Henrik Kniberg discusses the differences among different Agile processes such as Scrum, XP, and Kanban. He shares the thought that processes wars are meaningless and we need to see each process as a tool; there are no bad tools; just tools used for the wrong purpose.
Did you try pair programming but it didn’t work? Are you wondering if it’s worth it? In this live play you’ll follow a team as they go through stages and struggles of learning pair programming. You’ll see anti-patterns in practice so you can recognize them, and you’ll learn the small subtle things that is the difference between wasting time and a high productivity. Get the popcorn ready and open your mind. Pair programming can be a big boost – if it’s done right
Brian Spears shares his company’s adoption of extreme programming nine years ago and how his teams have evolved the process to suit their context. He shares the underlying keys to their success including management backing, the role and importance of a coach, and the eventual adaptation of XP with more experience. He also shares the non-XP practices and roles that evolved over the years.
Extreme programming sounds a little too “ESPN2″ for most managers, but there is a lot of sound engineering behind its principles. I talk about the parts of XP that are absolutely vital and the ones that you can introduce a little more slowly (pair programming, only a 40 hour work week). I also talk about political battles with managers, other departments, and barriers that pop up anytime you try to introduce change in a large enterprise.
Willem van den Ende and Marc Evers introduce different cultural patterns you can find in software organizations, based on Gerald M. Weinberg’s work, and tell how to recognize them, what behavior to expect, and how you can handle unexpected events and change. They show how different agile processes like Scrum, XP, and Lean Software Development fit in, while explaining some common agile failure modes.
Pairing can be a highly effective practice that adds significant value to a project, or it can be a disaster whose cost far exceeds managers’ fears that they are just paying two people to do the work of one. In the worst case, you won’t get the work of one out of the two. They might even do damage that others have to clean up later. The challenge lies in the fact that working as a pair demands a level of attentiveness, collaboration, and continuous focus that working solo just doesn’t require. We want to demonstrate some of the behaviors that can undermine the value of pairing, solicit audience feedback about their own experiences and observations, and explain how and why pairing works or doesn’t work. This session was first presented at Agile 2008, where a group of four people rehearsed and acted out “bad pairing” scenarios. In this case, the scenarios have not been rehearsed. Participants in the session will be asked to come forward to act out scenarios with the facilitator. Participants may also suggest scenarios based on their own experiences. Together, we will discuss approaches to correcting the unproductive pairing behaviors.
Robert “Uncle Bob” Martin looks into XP’s rearviewmirror, lessons learned, and the current status of Agile development. It has been 10 years since Extreme Programming broke upon our industry. In that time we have seen the rise of the Agile movement, and the gold rush for Scrum certification. We have seen the concept of testing do a complete reversal in emphasis; and shift away from heavy planning. But what have we learned? Do we really all program in pairs? Do we really all write our tests first? Do Agile projects really fare better than others? Do we have enough data now to separate the truth from the myth? And why, after all this time, does it still dominate our conferences and conversations. Isn’t there something new to talk about?
Lecture on Software Engineering by , Prof. Umesh Bellur, Department of Computer Science & Engineering ,IIT Bombay. The objectives are to are to explain how iterative and incremental development process leads to faster delivery of more useful software, to discuss the essence of agile development methods, to explain the principles and practices of extreme programming, to explain the roles of prototyping in the software process.
In this presentation, Kent Beck, the father of eXtreme Programming, shows the synergies between business and Agile development. The reason Agile is becoming more popular every day is because it responds to the business needs as they evolve.keep looking »