XP Seminar - Kent Beck  9-10th October

XP Explained: Values-Kent Beck

You cannot adopt a new culture without taking on board the underlying value system. Common values lead to quick consensus and easy co-operation, often without even needing to talk about it. We'll use stories to illustrate the four values of XP - communication, simplicity, feedback, and courage - as demonstrated by various kinds of XPers, business and technical.

XP Overview-Ian Mitchell

We will review the whole of XP so we can see how its parts work together to give a unified powerful whole methodology. We stress the need for agility to respond to a volatile business world and with the rapid learning both technical and customer staff experience in a new project.

The Planning Game -Kent Beck

We will run a real project with too much to do to demonstrate XP's dynamic planning technique. It will illustrate multiple releases, early feedback, re-prioritisation and all the complexity of managing many facetted dynamic projects. Above all the need for customer and programmers to be in the same room talking face-to-face is illustrated.

Pair Programming-Kent Beck

We will get you ready to run your own pair programming experiments. When are two people working in pairs more effective and efficient than when working separately? When they deliver defect-free software to a common understanding of the task, of the standards, and of the testing needed to prove the code is defect-free.

Test First Programming -Rick Mugridge

XP takes to the extreme what works. Test First works! Designing tests first clarifies the code structure and bounds. Defects are eliminated before they are written! So how do we take it to the extreme? Where do we stop? How do we know it is done? Does this approach carry overheads? What tools do we need? How does it relate to integration and acceptance testing? Is there anything you do not unit test?

XP on Wall Street -Steve Hayes

XP is being used for an ever growing range of applications. For a Down-Under viewpoint on managing XP projects Steve Hayes will speak about his experiences introducing XP into a Wall St bank for the development of both web based applications and three tier GUI applications. He will talk about the challenges of the transition and the benefits observed.

Refactoring & Architecture -Kent Beck

Can design emerge without centralized control? Can design occur in spite of a running system? Yes and yes. But not without a bit of effort. Can a palace be built starting with a shack? Do we design for the future or for now? When is Now not a necessary step to the future?

Managing an XP Project(Session designed for IT and Customer Management) -Kent Beck

Does management disappear in self-organizing teams? No. Governance is a crucial component of successful XP teams, but it takes the form of influence instead of control. Many managers need to learn new values and skills to create an environment for successful XP. Leadership, provisioning, rapid decision-making, staying in touch, focus on goals, avoiding by-ways and building the excitement - these are some characteristics of management that lead to success.

Optional Scope Contracts

XP gives the customer the assurance that they are only paying for work having immediate business value. The development team is highly responsive to the customer's needs. The customer has control over the deliverables. And even if the code is "wrong" it cannot have cost much before it is corrected. But the cost is an Optional Scope Contract and payment based on time alone.

Customer On-Site-Ian Mitchell

A critical factor in successful projects is close, clear, rapid face-to-face communication. Programmers and customers must educate each other on the task at hand and respond to changes in immediate needs. The "Customer" must also be able to get consensus from the business team on the requirements and take alternative solutions back to them.

XPNZ The Transition -Bryan Dollery

XP works, its way cool, its fun and exciting and we need to know about the decreased project times, the increased productivity and the increased quality. So why aren't we all doing it? This is a discussion placed in the New Zealand IT environment. It is about how to re-educate your internal or external customers. Change must be managed. It must have its champions, its agents, its tools and You must play the key role in making IT happen.

Recent Experiences -Kent Beck

Is the "typical" project changing? Have we done the huge ERP projects? Have we done the core business tasks? Are we now focussed on systems which respond to changing needs. Must we now be "agile"? Kent reviews some recent projects - A prominent Internet infrastructure company, A dot com, A project inside a corporate behemoth.

All the Rest -Ian Mitchell

We comment on the components not otherwise covered and discuss the issue - Do we need to do every part of XP or only the bits we like? In winning over the staff must we win every argument? Do all parts fit all projects? What tools do we need - if any? When not to do XP!

XP - The Future -Kent Beck

Is XP the Silver Bullet? Where can it be improved? Will XP be the normal way to tackle IT projects? Do we need tools specifically addressing an XP methodology? Can we instil the discipline into newbie programmers? How do we educate our customers? Where does XP clearly need to grow? Where might it be weak? Home