Short 4.1-4.3 Flashcards
Name the 3 agile scaling frameworks
- Large-scale Scrum
- Scaled Agile Framework
- Spotify Model
Explain the 3 agile scaling frameworks
Large Scale Scrum:
- non-prescriptive
- radical agile –> difficult to introduce to large firms
Scaled Agile Framework:
- big picture
- soft introduction
- very prescriptive
Spotify Model
- very agile
- limited detail on “how”
Risks associated with agile frameworks
- used as a silber bullet
- may limit the ability to discover other ideas
- prescriptive frameworks may solve a problem that is not the actual problem of the organization
Recommendations for adopting scaling agile frameworks
- common vocab
- continuous training to all staff
- conduct an organization readiness assessment to find barriers
Name fields of tension between agile methods and architecture
Agile Methods:
- bottom-up
- short-term oriented
- local and project-specific optimum
Architecture:
- top-down
- long-term
- global and company-wide optimum
Challenges of EA in large-scale agile development
- Balancing short and long-term planning
- Balancing architecture improvement and business value
- Dealing with loss of decision making power
- Dealing with not understanding of EA by agile teams
- Dealing with acceptance issues
Responsibilities of EA in large-scale agile development
- Collaborate with stakeholders to develop architectural roadmap
- collaborate with agile teams
- facilitate architectural decision-making process of agile teams
Challenges in working methodology of EA
- personal communication with agile teams over conversations based on documents
- creating simplest architecture upfront instead of big design
- leaving ivory-tower –> close collaboration
Expectations of agile teams regarding EA
- foster common understanding for architecture
- alignment of business and IT
- entrusting more architecture responsibility to agile teams
Tactics for better collaboration between EA and agile teams
Influence agile teams based on nudging
- show agile teams the benefits of complying with EAM measure
- use visuals and gamification approaches
- avoid financial rewards or punishment for non-compliance
Be a supportive EA
- provide technical guidance
- start with simple architecture upfront
- accept loss of decision-making power