Intro to Agile and Lean Software Development
•Download as ODP, PDF•
1 like•1,494 views
Basics of Agile and Lean presented at Agile Riga Day 2012 pre-conference warm-up meeting
![[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Intro to Agile and Lean Software Development
Similar to Intro to Agile and Lean Software Development (20)
More from Aleksejs Truhans
Recently uploaded
Recently uploaded (20)
Intro to Agile and Lean Software Development
- 1. AgileRigaDay 2012 Warm-up Agile and Lean Fundamentals http://www.agile-latvia.org
- 4. What bothers you most in your current situation?
- 8. Now at Citadele banka, tsi.lv, nh.lv, javaguru.lv
- 12. Properties of a ”good” process?
- 16. Discipline
- 17. Shared knowledge
- 18. Communication
- 19. Reflection
- 20. Fast feedback
- 23. The only detailed enough model is the program itself
- 24. We are producing decisions
- 26. Communicate
- 27. Decide
- 29. Communication?
- 32. people
- 33. problem
- 34. solution
- 36. Applicability: team size & cost of failure
- 37. How much effort do you waste due to wrong assumptions, bad design, etc.?
- 38. How much time do you waste due to inefficient process?
- 45. Jidoka: Autonomation, Stop the Line and Root Cause
- 47. W. Edward Deming and Eliyahu Goldratt
- 50. and decrease operating expense
- 51. all at the same time
- 52. The longest queue is right before the bottleneck
- 54. Not the lowest price but lower total cost through long-term relationships
- 55. Training on the job, education and self-improvement
- 56. Leadership instead of supervision
- 57. Eliminate management by objective
- 58. Eliminate management by fear
- 61. Eliminate barriers between departments
- 63. Extra features
- 64. Relearning
- 65. Handoffs
- 66. Task switching
- 67. Delays
- 68. Defects
- 71. minimize the size of things in process?
- 72. limit work to capacity?
- 73. reduce utilization of people's available time?
- 74. establish a regular cadence?
- 76. Frequent information transfer and integration
- 79. Expert workforce
- 82. Build quality in
- 83. Create knowledge through disciplined experimentation and retain it
- 84. Defer commitment, yet commit
- 85. Deliver fast
- 90. Design
- 91. Feedback
- 93. High-value items before low-value
- 94. High-risk high-value items before low-risk
- 95. Items that will create significant new knowledge before those already well understood
- 96. Items with lower cost to support and develop before higher cost
- 98. Pull the work. Limit the capacity.
- 101. Cadence taking form of average lead time
- 102. Estimations and target dates to be used appropriately
- 103. Service level lanes
- 105. Daily standup
- 106. Demo
- 107. Retrospective
- 109. Scrum master – removes obstacles
- 113. Assuming developers are eager to do the job, scrum fully loads them with most valuable tasks
- 115. Release planning
- 116. Iteration
- 117. Acceptance tests
- 120. Moving people around
- 124. New stories
- 127. Tom & Mary Popendiecks – Lean Sotware Development
- 128. Eliyahu Goldratt – Theory of Constraints
- 130. Edward W. Deming
- 135. Robert C. Martin