The document discusses the Kaizen lite model, a subset of the full Kaizen model. It summarizes that the support phase is the longest and most costly part of the product lifecycle, and that waste in the processes and technical debt in the product tend to grow over time under the standard model. It proposes using shorter development cycles, visibility tools like Kanban boards, and regular reviews of technical debt and waste reduction as part of the Kaizen lite approach. Key roles and their workloads are also defined.

1. Kaizen lite
S U B S E T O F K A I Z E N MO D E L
LEAN, ITERATIVE AND INCREMENTAL DEVELOPMENT

2. Lifecycle
Construction Support
• Construction – is just beginning for the project, majorify of time we would spend
maintaining it: bug fixes, small improvements etc.
• Support period (budget) is much more bigger than construction period (budget)
• With time - product tends to get more expensive to maintain
• Process tends to get more bureaucratic (business waste) and implementation tends to
deviate from agreed architecture (technical waste).

3. Challenges
Business
•With time - too many steps are introduced in the process
•With time - procedures tend to become complicated
•With time - amount of paperwork increases significantly
•With time - amount of reporting increases significantly
•Due to unbalanced process/procedure - sometimes people are waiting for work, or are overloaded with it
Technical
•Unhappiness with constant support which results in high attrition rate
•Lack of pride in workmanship results in lack of commitment
•High attrition rate results in constant training and lack of project knowledge
•Due to above – quality of code
•Small changes tend to break big picture (architecture)
Waste
v.1.0 v.2.0 v.3.0 v.4.0 v.5.0 v.6.0 ... Demise

4. Cycle
Requirements (egg)
• Business requirements
• Design
• Technical requirements
• Definition of milestones,
risks
• Estimation / cycle length
Construction (metamorphosis)
• Daily progress update
• Implementation
• Brief showcase of
milestones
• Optimization / Testing / QA
• Delivery
• Reflection upon cycle
• Due to relatively short duration of the
cycle – deep planning is not required.
• Due to relatively small size – extensive
testing and QA are not required.
• Due to relative simplicity – presentation
and complicated transition (delivery) are
not required.

5. Engagement
Project 1
Team SME Tech Lead BA PM TL
Project 3
BA PM TL
Project 2
SME Tech Lead BA PM TL

6. Kanban
Lack of visibility
Overload
Vision Construction
Vision Construction
Waiting
Lack of visibility
• Provide visibility of workload and current status of the milestones
• Provide visibility of progress and issues / blockers of process / procedures / systems
• Provide visibility of efficiency and improve if needed
• Waiting
• (waiting) Not on time
• (waiting) Not on budget
• Overload
• (overload) Not according to
expectation
• (overload) Lack of commitment
• (overload) Lack of pride in
workmanship
• (overload) High attrition rate
• (overload) Poor quality

7. Egg |
Meta|
Waste
Risks
Debt
Issues Debt
Checkpoint
Checkpoint
Perceived Debt vs Actual Debt Recycle plan
Waste reduce
Direction pair reviews Recycle log constantly and takes action to remove business debt
At least every third cycle - action items in Recycle log reviewed and implemented to remove technical debt

8. Summary
◦ Lifecycle
◦ Support is the most costly and lengthy phase of product life cycle
◦ Amount of waste in the process/product grows with time
◦ Challenges
◦ With time process/procedures tend to become complicated and amount of paperwork increases
◦ With time architecture tends to become „broken” and quality of code decreases
◦ Often people wait for work or are overloaded with it - due to unbalanced process/procedure
◦ Due to lack of pride in workmanship – unhappiness, lack of commitment and high attrition rate
◦ Kanban
◦ Provide visibility and control supply of milestones (work) to the Team
◦ Cycle
◦ Two phases: Requirements (Egg) and Construction (Meta) instead of standard four
◦ Cycle recommended length is 2 weeks
◦ Checkpoints
◦ It is recommended to have 2 checkpoints: 1h after Egg and 2-4h after Meta. Duration can be changed if cycle length is longer than 2 weeks
◦ Roles
◦ Vision pair (BA+Tech Lead) can work on multiple projects, but workload to be controlled to avoid overload (muri)
◦ SME’s and Tech Lead can work on up to 2 projects (based on Kaizen Lite). BA, TL, PM can work on up to 3 projects (based on Kaizen lite)
◦ Waste
◦ Direction pair reviews Recycle log constantly and takes action to remove business debt
◦ At least every third cycle - action items in Recycle log to be reviewed and implemented to remove technical debt
◦ Unless explicitly specified – existing guidelines of Kaizen model apply

9. IMPROVE
HTTP: / /PRYZACH.GITHUB. IO/KAIZEN-SWD-MODEL/
THANK YOU