Agile Architecture Retrospective
2 likes601 views
The document emphasizes the importance of fostering an agile organizational culture through self-organizing teams and various agile practices. It outlines strategies for enhancing software agility, including team coaching, architecture retrospectives, and the significance of aligning values, principles, and practices within agile methodologies. Additionally, it highlights the role of software craftsmanship in improving development processes and encourages a continuous learning mindset among developers.
Agile Architecture Retrospective
- 1. Me • Focus on building an organization culture to "be agile" rather than "follow Agile". • Software agility delivered through team agility • Team agility delivered through coaching teams to be self-organized • Self-organized teams using agile tools, techniques and technologies. Agility Services Software Craftsmanship Midas Touch - Agility in software maintenance Agile Enterprise Architecture solutions Agility Nurseries (Agile ODC) Organization Metamorphosis Agility Assessment Radars and Roadmap Team Agility Assessment Value Stream Mapping Shared Vision and Team Chartering Team Agility Coaching, Executive Coaching Scrum Coaching XP Engineering Practices Coaching Lean Software Development Coaching
- 2. Agile Architecture Retrospective An Inspect-N-Adapt Tool For the Enterprise
- 4. Primary Scope Building a motivated, self-organizing architecture team • Motivated Individuals • Self – Organizing Teams • Architect Persona Retrospective on architecture Secondary Scope Software Craftsmanship and Architecture Introducing Agility in Enterprise Architecture
- 6. Values, Principles and Practices : Relationship
- 7. Values, Practices and Principles : Relationship Values bring purpose to Practices, Practices are evidence of Values, Practices bring accountability to Values. Bridging the gap between Values and Practices are Principles. Principles are context specific guidelines. e.g. practice Pair Programming values “communication” and “feedback” principle driver-navigator principle – dual thinking hats of constructing and preventing from breaking. practice Companion Planting used in agriculture values “sustainability” and “responsibility” principle Diversity is nature's design, cooperation is more apparent than competition in plants, crop stability tends to increase with increasing diversity. Sources: - Extreme Programming – Embrace Change by Kent Beck Intercropping Principles and Production Practices by National Sustainable Agriculture Service
- 8. Discuss with your partner An instance of mapping a practice to its underlying values and principles
- 9. Values, Principles and Practices Of A Manifesto
- 10. (based on a commonly agreed set of values) Source: - TheFreeDictionary.org
- 12. Layers of the Agile Manifesto Agree to disagree on detailed project specific ground tactics and prescriptive Barely agree on 12 Agree on 4 Agree on the meaning of “Agile”
- 13. Individuals and Interactions (amongst Individuals) Values
- 14. Value - Individuals and Interactions Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
- 15. Discuss with your partner 1. An Instance of Creative Cycle practice 2. An Instance of Survival Cycle practice That maps to the motivated individuals principle
- 16. Value - Individuals and Interactions Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
- 19. Probably A Software Architect Manifesto Candidate Accounting cost-of-change in upfront decisions over documenting architecture Live real-time documentation over comprehensive encyclopedias and glossaries Architecting non-functional requirements early over optimizing at the end Evaluating technology to business needs over latest buzzwords solution (Just because it looks good on your resume / CV) Exploratory pointers / solutions over "It depends" consultant syndrome Experimentation over freezing on design early in product lifecycle Executable skeleton code over discussions, meetings and diagrams Team collaboration over solo architecture responsibilities Collective accountability over responsibility delegation to implementation team Coaching team members over individual knowledge consolidation Pragmatism over perfection Real problems over intellectual (self) stimulation Simplicity and common sense over complexity in ideas Reference: - CodingTheArchitecture.com (Simon Brown)
- 20. Definition Of An Architect Discussion
- 21. Being An Architect “Crown” OR “Cap” Title OR Role
- 22. Craftsperson Craftsmen Agile Architects
- 24. Architect to Craftsperson What is Software Craftsmanship? “Software Craftsmanship is all about putting responsibility and pride back into the software development process. ” “The best processes in the world will not save a project from failure if the people involved do not have the necessary skills to execute the process; conversely, really good developers can make any process work” “A Software Craftsman is a continuous learner. When he doesn’t work, he spends his time studying, to find new methods and tools can refine him as a Software Craftsman” - Pete McBreen, Software Craftsmanship: The New Imperative Software Craftsmanship is about Taking responsibility Taking pride in work “Signing” your work Being a continuous learner Practicing deliberately Writing code Having the right attitude Contributing to the community
- 25. Architect to Craftsperson through Apprenticeship How should I become an expert in software craftsmanship? Read and understand the concepts on Apprenticeship Patterns - David Hoover, Adewale Oshineye Find a mentor Study, Train and Practice Performing Code Katas Performing Coding Dojos Performing Acceptance-Test based Learning TDD Learning programming paradigms – functional, dynamic, statically typed languages Refactoring – keep your code healthy Learning design patterns, tools and frameworks Learning emergent design, evolutionary design
- 26. Architect to Craftsperson How will I know the learning levels in software craftsmanship? Dreyfus Model of Skills Acquisition Novice - Needs to be told exactly what to do. No context to work from. Advanced Beginner - Has more context, but needs rigid guidelines Competent - Questions reasoning behind the tasks and can see consequences Proficient - Still relies on rules, but can separate what’s important Expert - Works mainly on intuition, except when problems occur
- 27. Finding Your Own Identity is about Metamorphosis (Shu – Ha – Ri) From Architect (Crawling Caterpillar) to Leader Craftsperson (Soaring Butterfly) Creative Cycle To Follow Agile To Be agile Responsibility Apprenticeship Pride (“Signing” Your Work) Collaboration Continuous Argumentation Learner Novice Advanced Beginner Competent Conflict Mining Deliberate Proficient Practice Team Intelligence Expert Right Attitude Psychological Distance Follower Volunteer Mentor Community Solvent Contributor
- 28. Agility in Enterprise Architecture A Healthcare Systems Case Study