Virtually every leader and organization that has adopted agile and iterative methods, including the recent Yahoo adoption of Scrum, will vouch for the high-impact value in having an experienced coach help kick start the adoption of these practices on a pilot project, which often involve significant and sometimes subtle changes in how to approach project planning, requirements analysis, test, and measurement. Thus, in addition to the first step of helping executive management understand the motivation, evidence, and big ideas regarding agile and iterative methods, in the second step I help these organizations launch a pilot project through my Agile Iteration KickStart program.
This has some similarity to my highly-customized mentoring package, but the KickStart is a more structured 5 or 10-day workshop centered around your project.
In short, the KickStart takes the team through some “classic” events and activities of an iteration, such as iteration planning, requirements or design workshops, and more. This often revolves around the (extremely) popular Scrum method, but other methods, such as XP, FDD or Crystal, can form the foundation if you desire. I’ll (or one of my very talented coaching colleagues) be spending significant time with a cross-functional team, coaching them through the details of perhaps a requirements and/or design workshop, and the iteration planning meeting. I’ll be spending time with the team and business stakeholders to help understand and apply Scrum skills, and chart progress with iteration and release burn-down charts. I’ll be working with developers at their workstations, and in small teams at the whiteboards during object design and agile modeling sessions, also perhaps coaching test-driven development or refactoring.
Discussion, presentation, Q&A, workshop exercises
Clients find it useful to include related product groups; for example, 8 people from 1 product, and 8 from another. It is useful to include a cross-functional set of representative skills (product management, development, test, systems engineering, ...) as lean and agile principles emphasis cross-functional teams and very close, cyclic collaboration between product management and R&D.
Intermediate: This course introduces concepts and techniques that the attendee will apply during the workshop.
The intent of this session is to begin using agile development techniques in real life--you should have a real project and a real development environment to get the most of this time. Good preparation beforehand significantly improves the richness of the outcome.
It is highly recommended that you have attended Agile Software Development: Hands-on Practices, Principles, Agile Modeling, and TDD beforehand.
Depending on topics selected, after completion of this course students should be able to:
Several schedule variations are possible and will be customized with you beforehand, depending on the degree of requirements and design fuzziness and complexity, and state of the team. For example:
Another popular variation runs 3 mini-iterations on the development project Tuesday-Thursday.
I emphasize not only analytical skills such as requirements and design patterns, but harder-core engineering skills such as setting up and using a continuous integration and test environment, test-driven development, pair design, light-weight code reviews, and more. There are myriad skills that may be applied and mastered. Depending on your needs, that may include:
Read this: Course Environment - Workshop Style3
Text and Notes