Today's show is all about Agile as a project management tool, and second how to use it in New Offer (Product or Service) Development.
It is the ultimate co-development tool - when you need to build something when the charcaterisitcs of the offer are unknown. Agile is a complete process for Exploring an Idea, Designing & Developing it, and Testing the Beta Version prior to release.
Given shows 7, 23, and 35, create a plan for incorporating customers (and sometimes suppliers) in your projects for improving or creating a new offer.
EPISODE 177: Summary
Agile is a topic we have discussed in many different shows over the last 2 years. Today I am going to hit the highlights and get you ready for next weeks show on Co-Development.
The best description is an iterative (a series of steps you repeat, tweaking and improving the product or service under development to make it as perfect as possible) project process performed in a collaborative environment by self-organizing teams.
It had its origins in software where developers and users would sit side-by-side, writing code and testing almost at the same time. It created better software faster and at lower cost. It has been adopted by many industries and is a powerful approach to developing new products and services.
EPISODE 178: The Agile Project Cycle
The Agile Project Cycle is the structured series of stages that a product or service goes through as it moves from beginning to end. It contains five phases: planning, designing, execution, testing, and deployment or release.
EPISODE 179: The Agile Tools
The tools used in the Agile process is really not much different than other project management approaches. The biggest difference is with traditional project management you know the desired outcome and the focus is on cost containment and delivering on budget.
When employing the agile approach you don't know what the final output will be so you focus on a repeatable process that will produce the best possible result. Your focus is on accuracy and speed.
EPISODE 180: The Agile Players
The names of these players might seem different, but when you look at the roles these are usually contained in any serious project management effort.
The major difference is sticking to the process and allowing the teams (Sprints) to self-organize based upon the current backlog item and who is in attendance at that point in time.
Next Show/Chapter 43: CO-DEVELOPMENT WITH CUSTOMERS AND SUPPLIERS
How to apply today's show to your business:
new choice for BUSINESS SEARCH