Agile Startup Workshop
Getting an Agile software development effort started, without a lot of guesswork, is a real challenge. We're experienced in getting companies started with Agile. In this workshop we guide your team through the key activities to get an effective iterative development plan in place. No toy projects are used here. We use your product and develop its backlog. This workshop usually lastS 3 days, depending upon team size and preparation. Before the workshop a preparation package is completed by the team to fuel a very effective workshop.
How Does this Workshop Differ from Scrum Training
There are a number of differences.- This workshop is designed help you start iterative development on your product. Exercises are not done with a toy example.
- Breaking your work into stories, especially for embedded systems is a challenge. Our workshop facilitators can help you figure out how to break your work into a series of incremental deliveries that demonstrate progress or deliver value to your end customer.
- You won't get a Scrum Master certificate, though you can have a Wingman Software Certificate of Completion.
Facilitator Led Activities
- Articulate Goals
- Identify Stake-holders
- Create Story Backlog
- Architectural Vision
- Identify Team Members and Roles
- Create Initial Estimates
- Create Initial Release Plan
- Create agile transition backlog
Attendees
This workshop is typically done for an single product team. A second team or individuals could participate, though we focus on one product. Adopting an Agile way to work is not just an engineering issue. This workshop should be attended by a cross-functional team, including:
- Management
- Marketing
- Engineering
- Systems engineers
- Customer service
- System test
Most teams are ready to start iterating the day after the workshop.
Prerequisites
Engineers should have been though one of our Test-Driven Development Courses. This is important because test automation is foundational to success in adopting an iterative and incremental development model like agile.
Workshop Outline
- Agile Overview
- What Problems Does Agile try to Solve?
- What is Agile?
- Why Iterative and Incremental?
- Agile planning, Tracking Concepts.
- Collaboration, and Self Organizing Teams
- Scrum vs Extreme Programming Terminology
- Engineering Practices of Extreme Programming Briefing
- Iteration Zero Game Plan
- Product Vision and Team
- Concepts and Approach
- Do it for your product.
- Breaking Down Requirements into Stories
- Concepts and Approach
- Do it for your product.
- Estimation and Release Planning and Tracking
- Concepts and Approach
- Do it for your product.
- Iteration Planning
- Concepts and Approach
- Do it for your product.
- Automated Acceptance Testing
- Concepts and Approach
- Determine options for your product.
- Agile Transition Backlog
- Agreement on things to do and try
- Identification of skills to develop
- Workshop Wrap Up
- Other topics as needed and time allows
Typical Workshop Timing
Each workshop is custom to your needs and pace. The workshop is not done on a hurried pace. We often have time on the third day for deeper dives in to topics that are foremost in the team's mind. Here are some typical timings.
Latest News
Conference Video - Deep Stack – Tracer Bullets from ADC to Browser
A blank page can be very intimidating, even for a Test-driven developer. Where do we start? Write a test, right? Not always.
more...Podcast on Agile Amped
Here is a short interview with James about TDD and embedded software from the deliver:Agile conference last spring.
more...Programming Research -- Please Participate
Do you have some time to do a simple programming problem in C or C++ for my research?
more...Clean Coders IoT Case Study
My long-time good friend (Uncle) Bob Martin and I have fun programming together firing tracer bullets for distributed water pressure measurement system.
more...Books
James is the author of Test-Driven Development for Embedded C.
Have you read Test-Driven Development for Embedded C? Please write a review at
Amazon
or
Good Reads
.