Lean methodology
- Identify value streams
- Maximize value to customer
- Optimize the value streams
- Recognize how to optimize stream
Lean principals talk about identify wastage based on below principals
- Is a customer willing to pay for something?
- If not, then this is waste
- Typical signs of waste
- Large amount of Work in Progress
- Unwarranted context switching
- High manual effort
TO avoid this waste
- Minimize errors in value streams
- Automate
- Standardize
Lean principals also encourage rapid delivery.
In lean you must create knowledge.
- Apply iterative learning
- Analyze results of incremental work
- Share learning experience
- Implement infrastructure to capture knowledge
Another principal of lean is Defer commitment
- Just-in-time systems.
- decisions made as late as possible
- Maximize decision-making agility
- Relevant Information
- Timely information
Lean principal: Respect people
- Respect employees
- Respect customers
- Respect co-workers
Agile Software developlement process
- Work backlog
- Sprint backlog
- Sprints
- Incremental delivery
Key features
- High adaptability to change
- No in-depth planning at onset
- Continuously changing requirements
- Customer feedback loop
- Work is prioritized to maximize customer value
- Incremental and iterative approach
Key methods to Apply
- Kanban
- Scrum
- Extreme programming
Agile Manifesto
- Human interactions
- Functional software
- Customer relationships
- Adaption to change
Principle of building strong team
- Empower and support employees
- Enable the team self-organization
- Work closely with subject matter experts
- Encourage face-to-face interactions
- Promote sustainable development
- Tune and adjust behavior frequently
Principles for client focused attention
- Encourage changing requirements from customer
- Focus on customer competitive advantages.
Agile with Scrum
- Work backlog
- Sprint backlog
- Sprints and Scrum meetings
- Incremental delivery
Key scrum roles
- Product owner
- Scrum master
- Scrum team
Scrum work flows
- Sprint planning
- Daily Scrum
- Sprint review meeting
- Sprint retrospective
When Agile prefereable
- Customer availability
- When scope is unknown upfront
- Where partial success is valuable
- When the team is small and highly skilled
- When funding is flexible
When Agile
- THe project is based on predictive and repeatable work
- The project is not very urgent
- The project is complex or novel
- The team is not confident in self-organization
- The team lacks professional developers
- The customer requires elaborate documentation
- The customer requires to approve all work.
- There is a lack of culture promoting Agile practices