Agile software development means that you provide the client what (s)he doesn’t want in the first 30 days rather than after 180 days. You use the remaining 150 days to build what the client really wants with a “show as you go” strategy following each 30 day iteration.
In 2001, Ken Schwaber, Kent Beck, Martin Fowler and Alistair Cockburn amongst others came up with the Agile Manifesto as follows: We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: - Individuals and interactions over processes and tools - Working software over comprehensive documentation - Customer collaboration over contract negotiation - Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more. On face of it the manifesto may seem like an excuse for chaotic hacking, and perhaps fine with small teams, but not for serious development. However, since most of the world’s 15 million software developers usually work in small teams of around 3 to 5 people; “Agile” has resonated far and wide to good effect.
Agile Vancouver kicked off in October, 2005 with a presentation by Alistair Cockburn. Since then it has featured speakers on a regular basis with a usual turnout of over 50 software developers and managers. The group continues to flourish and feature presentations and courses from leading practitioners around the world.
Of course our "network" is about more than just our meetings. Beyond our members' personal networks we have an opt-in mailing list plus our groups on LinkedIn, Facebook, and Yahoo! See our About Us page at http://www.meetup.com/Agile-Vancouver/about/ for more detail
Seven Lightweight Tools for the Business Agilist Toolbox
As agile teams shift away from comprehensive documents and tools, there is still a need for lightweight analysis tools help agile teams structure collaborative conversations.
In this session, Roger Burlton, a pioneer in process management and the Author of the Business Process Manifesto, will introduce seven key techniques that will help your clients to understand what’s going on and participate easily in requirements conversations. We guarantee that you will want to and will be able to use these over and over again. During this workshop, you will have the opportunity to apply these techniques using a simple case study.
Stakeholder Exchanges, Expectations, and Experiences
Concept / Information Maps
The Process IGOE Model
Multiple Dimensions of Measurement
Culture and Behaviour Design
The Burlton Hexagon for Capability Assessment