Architecture in Agile projects - course RUB 32,900. from IBS Training Center, training 16 hours, Date: December 3, 2023.
Miscellaneous / / December 03, 2023
Very often, when implementing Agile, there is no understanding of how to combine the postulates and recommendations of Agile with the theory and practices of architectural design and architecture management. In some cases, the need for architectural practices is denied, even in large projects, which, of course, does not lead to anything good. In fact, there is no contradiction between the practices of Agile and architectural design, and all developed Agile frameworks recognize this and designate places and roles for architectural work. This course continues the ARC-001 course, which only touched upon this problem, and studies this topic in detail. The relationship between Agile and architectural practices is analyzed, it is found out why and how they complement each other, what they can achieve cause distortions in one direction or another and how practically it is possible and necessary to adapt architectural practices in Agile context. Practices such as: analysis of requirements in conditions of their incompleteness and constant change, making architectural decisions (with taking into account risks and trade-offs), documenting and self-documenting the project, as well as architectural supervision and review using techniques Agile. The course combines both theoretical introduction and practical development of design analysis skills context, risks, as well as technical and organizational design skills within the framework of the topics
Course program
Topics covered:
1. Features of architecture in Agile (1 hour)
History of Agile.
Architecture in Agile: from denial to a risk-driven architecture model.
2. Agile architecture concepts: RAD, SAFe (2 hours)
Risk-Managed Architecture.
Architecture of highly variable systems.
The role of the architect in SAFe.
3. Working with architecturally significant requirements (3 hours)
Architecturally significant requirements.
Key scenarios.
Basic functional requirements, non-functional requirements.
The “If it's non-functional, why do I care about it?” approach.
Restrictions on User Story, Enablers, Techdebt Stories, Landing Zone.
Architectural restrictions.
4. Decision making process, architectural styles (3 hours)
Iterative decision-making process (light versions of ADD).
Fast simulation.
Applying styles and templates with examples (microservices).
5. Documenting solutions: NoUML, “live” documentation (2 hours)
Context, perspectives (Perspective).
NoUML: C4 and LADR.
"Live" documentation.
Antipatterns.
6. Team organization, scalable Agile (2 hours)
Conway's Law.
Two approaches: from the architecture or from the existing team.
Antipatterns.
7. Architectural supervision using CI and UT tools (1 hour)
Key mechanisms.
Architectural code review.
Architectural unit tests.
Static code analyzers, metrics.
Fitness functions.
8. Review of architectural solutions (2 hours)
LAAAAM.
TARA.
All information published in this section of Lifehacker is not a public offer as defined by the provisions of Article 437 of the Civil Code of the Russian Federation, and is for informational purposes only.
The service uses technologies from the “Educated” project and does not provide educational services.