Skills for the agile designer: seeing, shaping and discussing design ideas
Proceedings of the ACM international conference companion on Object oriented programming systems languages and applications companion
Architecting with just enough information
Proceedings of the 6th International Workshop on SHAring and Reusing Architectural Knowledge
Analyzing the drivers of the combination of lean and agile in software development companies
PROFES'12 Proceedings of the 13th international conference on Product-Focused Software Process Improvement
Survey on agile and lean usage in finnish software industry
Proceedings of the ACM-IEEE international symposium on Empirical software engineering and measurement
Proceedings of the 3rd annual conference on Systems, programming, and applications: software for humanity
The data, context and interaction paradigm
Proceedings of the 3rd annual conference on Systems, programming, and applications: software for humanity
HCSE'12 Proceedings of the 4th international conference on Human-Centered Software Engineering
Design patterns as first-class connectors
Proceedings of the 2nd annual conference on Research in information technology
The lean gap: A review of lean approaches to large-scale software systems development
Journal of Systems and Software
Architecting automotive product lines: Industrial practice
Science of Computer Programming
Hi-index | 0.00 |
More and more Agile projects are seeking architectural roots as they struggle with complexity and scale - and they're seeking lightweight ways to do it Still seeking? In this bookthe authorshelp you to find your own path Taking cues from Lean development,they can help steer your project toward practices with longstanding track records Up-front architecture? Sure. You can deliver an architecture as code that compiles and that concretely guides development without bogging it down in a mass of documents and guesses about the implementation Documentation? Even a whiteboard diagram, or a CRC card, is documentation: the goal isn't to avoid documentation, but to document just the right things in just the right amount Process? This all works within the frameworks of Scrum, XP, and other Agile approaches