About the Book
Keeping an efficient Software Architecture can save you a lot of time, and also help build the foundations of a successful Software Project. But, how to set up a way of working that is at the same time efficient, easy to implement and compatible with Agile methodologies? That’s what you’ll learn with this book.
Who is this book for?
All kind of Software Architects (Solutions, Enterprise) and Software Developers who are interested in improving their ways of working regarding Architecture: Software Design, Decision Making, Traceability, Efficiency, etc. All in a pragmatic manner.
Especially useful for:
- those who already identified issues due to not having a process at all, following a Fake Agile Architecture or a Heavy and Boring process;
- teams that don't have a good decision-making mechanism;
- software architects starting a project from scratch and
- people having to spend a lot of time in non-productive tasks due to ineffective ways of working with Software.
- Why do you need a Software Process?
- The process stigma: this sounds boring
- Process Outcome: The Architecture Guide
- The Practical Architecture Process Overview
- Block I: Vision and Constraints
- Block II: Architecture Roadmap
- Block III: Decision Making
- Wrapping up
About the Author
I'm developing software since I was a kid, when my parents bought me a Spectrum ZX (in which I also played great videogames...). I've worked at startups, where a developer is a real full-stack developer (from frontend to backend, from building to maintaining, from the cave to customer-facing meetings) and also at big companies, where stability and keeping high product quality standards is a must. Along my career I have been involved usually in development, design and architecture, for small and huge projects. Worked in waterfall and agile environments.
Now I'm working at a Dutch company as Solutions Architect for a project based on microservices. I like keeping ways of working as practical as possible but, at the same time, producing proper documentation and sharing knowledge.