Presentation from AgileSparcs 2014
Agile techniques have been developed for last years. Less attention was paid to architecture. Original architecture methods take months and aren't adopted to modern development cycles. Software maintenance cost grows exponentially with a time and exceeds expectations. Customers and market require fast delivery of valuable and quality software.
Managing a software development becomes a complicated task. Is possible to keep the balance between fast moving and planning? What are tools of lean architecture to help us?How architecture integrates into agile software development cycles and helps to build quality software with low risk?
2. Code Quality
● Core value of SAFe
● Critical for scaled R&D
● Cumulative effect of errors
● Maintenance cost
● R&D risks
3. Get the right tool
● Plan doesn’t work
● Time isn’t enough
● Training doesn’t help
4. Plans are Useless
● Roadmap changed continuously
● Future plans ignored completely
“In preparing for battle
I have always found that
plans are useless,
but planning is indispensable.”
-- Dwight D. Eisenhower
5. Does Architecture slow down
● Everyone wants but no one does
● Balance of fast move and planning
6. What is architecture
● Harmony of Ease, Use & Quality
● Enabler for long distance development
● Tool to simplify tasks
... is the process of defining a structured solution ...
Microsoft MSDN
… is the structure or structures of the system …
Software Architecture in Practice (2nd edition),
Bass, Clements, Kazman; Addison-Wesley 2003
... is a framework for change.
Andreas Rausch (Professor, Technische Universität Clausthal)