The role of the architect in agile
•
0 likes•269 views
In Agile development, architects still play an important role by setting constraints and principles to provide guidance and boundaries for development teams. While Agile values working software over documentation, architects can document architecture decisions and provide guidance through code examples. On Agile teams, the architect acts as an owner who facilitates architectural decisions, explores new technologies, and evolves the architecture over time based on learnings. The architect also helps align development across teams when needed.
More Related Content
What's hot
What's hot (19)
Similar to The role of the architect in agile
Similar to The role of the architect in agile (20)
More from Dror Helper
More from Dror Helper (20)
Recently uploaded
Recently uploaded (20)
The role of the architect in agile
- 1. The Role of the Architect in Agile Dror Helper | @dhelper | http://helpercode.com Practical Agile
- 2. Consultant and Software Architect Developing software since 2002 Clean Coder & Test Driven Developer Pluralsight author https://www.pluralsight.com/authors/dror-helper B: http://helpercode.com T: @dhelper About.ME
- 3. “ ” Architects make high-level design choices much more often than low-level choices. In addition, the architect may sometimes dictate technical standards, including coding standards, tools, or platforms. Wikipedia: Software architect
- 4. The Agile Manifesto Individuals and interactions Over processes and tools Working software comprehensive documentation Customer collaboration contract negotiation Responding to change following a plan
- 5. Extreme Programming (XP) The Planning Game Small Releases Metaphor Simple Design Testing Refactoring Pair Programming Collective Ownership Continuous Integration 40-hour week On-site Customer Coding Standard - Do we still need an architect?
- 6. In (A)TDD - do we still need an architect?
- 7. Architecture is needed Gather functional requirements Decide on quality attributes Set constraints Create principles
- 8. “ ” The point is that you now have a framework and some boundaries to work within, which provide some often needed vision and guidance for the team. Simon Brown http://www.codingthearchitecture.com/2014/02/19/software_architecture_provides_boundaries_for_tdd_bdd_ddd_rdd_and_clean_code.html
- 11. “ ” While we must acknowledge emergence in design and system development, a little planning can avoid much waste. James O. Coplien, Lean Architecture
- 12. Agile Architecture Setting up Construction Iteration 24h Architectural vision • Facilitate architectural decisions • Explore new technologies • Evolve architecture based on learning • JIT Modeling Prove using code Backlog Tasks Learn and adaptPlan
- 14. Documentation and Diagrams IEEE software life cycle SQA Software quality assurance IEEE 730 SCM Software configuration management IEEE 828 STD Software test documentation IEEE 829 SRS Software requirements specification IEEE 830 V&V Software verification and validation IEEE 1012 SDD Software design description IEEE 1016 SDD Software project management IEEE 1058 SUD Software user documentation IEEE 1063
- 15. Agile Documentation YAGNI! Only document what you need • Consider the reader Provide guidance using code • Describe using documentation what you can't get from the code Document what you must due to regulations, contracts etc. • But make sure you have to
- 16. Architecture by exampleCreate vertical slices Show use of technology Provide coding standards Only develop enough code to solve a problem or provide guidance
- 17. The Architect Place in the Agile Team
- 18. Agile Teams • Small group of people • Assigned to the same project or effort • Shared responsibility • Posses all of the necessary competencies • Roles and responsibilities do not matter as much as results
- 19. Option 1 - Everybody an architect • Small company • Experienced developers • Mature developers • Ability to self govern
- 20. Option 2 – Architecture Owner • Small company • Clear architecture • Different skill levels/experience • Align development within the team
- 21. Option 3 – Architecture Owner Team • Centralized standards • Align architecture for every team
- 22. Top 10 list of things for a solution architect to be successful in an agile team • “Just enough” upfront design • Start with a vertical slice • Just-in-time design each iteration • Trust your team… but be there for them • Write code! • Be involved in everything • Drive a culture of quality • Know when changes are required • Shield the team from external randomization • Write docs … but only if someone needs to read them Tom Hollander
- 23. Thank you Dror Helper | @dhelper | http://helpercode.com