Best practices for agile design
•
9 likes•2,588 views
Agile design focuses on responding quickly to change, prioritizing customer needs, and designing systems that can evolve over time through continuous feedback and incremental changes. Key practices include minimizing upfront design, designing for reversibility and feedback, vertically integrating work in short cycles, and distributing design decisions across self-organizing teams. The goal is to safely deliver value while learning through doing rather than extensive pre-planning.
![Agile design Best practices We believe that it is possible. Igor Moochnick Principal IgorShare Consulting [email_address] Blog: www.igorshare.com/blog](https://image.slidesharecdn.com/bestpracticesforagiledesign-110512193050-phpapp02/85/Best-practices-for-agile-design-1-320.jpg)
![A/agile? L/lean? ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (8)
Similar to Best practices for agile design
Similar to Best practices for agile design (20)
More from Igor Moochnick
More from Igor Moochnick (20)
Recently uploaded
Recently uploaded (20)
Best practices for agile design
- 1. Agile design Best practices We believe that it is possible. Igor Moochnick Principal IgorShare Consulting [email_address] Blog: www.igorshare.com/blog
- 10. Transparency - Feedback Not Started In Progress Testing Customer Review Done, Done, Done Story #1 Story #2 Story #3 Story #4 Story #5 Story #6 Story #7 Story #8 Story #9 Story #10
- 22. SOLID Development Principles (classes)
- 28. Package Cohesion Principles REP The Release Reuse Equivalency Principle The granule of reuse is the granule of release. CCP The Common Closure Principle Classes that change together are packaged together. CRP The Common Reuse Principle Classes that are used together are packaged together.
- 29. Package Coupling Principles ADP The Acyclic Dependencies Principle The dependency graph of packages must have no cycles. SDP The Stable Dependencies Principle Depend in the direction of stability. SAP The Stable Abstractions Principle Abstractness increases with stability.
- 34. Tests are all about confidence
Editor's Notes
- A class should have one, and only one, reason to change
- You should be able to extend a classes behavior, without modifying it "Software entities should be open for extension, but closed for modification.“ - Robert C. Martin “… the essence of the Open/Closed Principle is being able to add new functionality to an existing codebase by writing completely new code with minimal modification of existing code. ”
- Derived classes must be substitutable for their base classes.
- Make fine grained interfaces that are client specific.
- Depend on abstractions, not on concretions