Episode B.037 Project Teams Are The JIT

Introduction
Even though the new quarter doesn't start until Wednesday, we are jumping into it with both feet. BTW - that is also the theme for July - Being Agile. Two quick reasons for this theme now. First is we are in new territory when it comes to the economy, social factors, government action and how it is affecting our ability to run a profitable business. The second is how it matches with our previous emphasis around building a "Lean Organization'. The difference is simple - Agile is a mindset that uses the principles of Lean to succeed in unstable times.
​
Show Objectives
Today's show is picking up on the out-of-the-box idea presented earlier today (A.037).  The idea was simple - instead of investing in infrastructure during the early stages of growth as well as transforming to an Agile philosophy. 

What if we matched sales forecasting and project management as a method to build JIT (Just In Time) capacity to meet any demand immediately - or close to it?

The goal for today's show is to explore how Agile Teams are a JIT resource.

What You Need to Know
The following links are a quick review of the concept and the necessity of having a JIT capability in the business. 

• EPISODE B.001 PRINCIPLES OF LEAN THINKING
• EPISODE B.002 UNEVENNESS OR MURA
• EPISODE A.035 LEADING YOUR MARKET BY BEING AGILE

Critical Roles

• SCRUM Master (Facilitator): ensures project Sprints are delivered on budget (Financial Representative) - great role for the owner;
• Technical Expert: ensures products/services are built correctly and to technical standards (Process Representative);
• Product Owner: ensures the product/service is built to customer specifications (Customer Representative);
• Subject Matter Expert (SME): provides specific expertise on a technology or industry.

​What You Need to Do

1. Understand the QFD Process - download attached file below. This is the only real structure you need to provide. This process is organized by the SCRUM Master and executed by the Tech Expert, the SME, and the Product Owner. This ensures the Project and its Sprints are focused on delivering the right end product.
2. Scheduled and in Queue - EPISODE B.002 UNEVENNESS OR MURA
3. WIP: Project Starts in a series of Sprints each Timeboxed. This is an agreed upon amount of time where the focus is on completion of this Sprint - which stops at the end of the period. Instead of continuing to work until completed, this means when the time is up it is up. 
4. Review: The Sprint is then evaluated and results incorporated in the next Sprint. This process continues until the entire project is completed - which was also Timeboxed.
5. Acceptance: Project meets preset Standards. ​

​

Next Show: B.038 Action Over Structure

qfdnewproductmatrix.pdf
File Size:	49 kb
File Type:	pdf

Download File

---