Flexible technologies: Extreme Programming and Unified Development Process (Agile Modeling: Effective practices for XP) (Category Management)
Retrieved from the shelf a rare book by Scott Ambler (Scott Ambler)which I read back in 2005 At the beginning of his career as an engineer. At that time, everyone did not pray at Agile Manifesto, the cascading development was still in perfect order, and a unified development process for the RUP species was walking around the world. (Rational Unified Process). And in this book, the author tried to share his experience in software modeling. In the end, the book was 400 pages, 30 Chapters and Five Parts That Are Worth Detailing 1. Introduction to flexible modelling - here the author talks about agile manifesto and on the basis of it formulates his principles of agile modeling, such as that one should expect change, change should be done small, we need many models, quick feedback, that content is more important than form, and so on. Next, the author talks about different modeling methods: incremental, group work, the importance of testing the model and checking it in code, use modeling standards and do not get carried away with patterns. This part was very helpful to me almost. 20 years ago 2. Flexible modelling in practice - it all starts with the importance of communication for software modeling, then debunks the myths of the type "requirements freeze" or "engraved in stone design", then mentions the modeling of the interface, requirements, writing documentation, and the use of notations - then UML was ahead of the planet, but already in this book there was a chapter called "Beyond UML":) 3. Flexible modeling and extreme programming Here the author is considering XP. (extreme programming) It shows how agile modeling fits into this approach. You can see from this book that XP was on the line at the time and it was important to refer to it, not Scrum, Kanban or anything else. 4. Flexible modeling and unified process And here the author is talking about a unified process, which will then become RUP (rational unified process). This is another part of the spectrum where we look at the bureaucratic process that has replaced the cascading one. The author shows that agile modeling can be useful here. 5. Looking to the future In this part, the author talks about how to implement software modeling in their processes.
In total, the book for its time was very good - a qualitative conversation about modeling and software design, a discussion of how it is built into the then development processes. Discussion of practical approaches, tools, notations and so on. I learned and learned a lot from the book at the time. But now this book is more of a dinosaur from the past and should only be read by archeologists of development processes or by nostalgic people like me:)
P.S. Interestingly, the author of the book, Scott Ambler, went on to dig into the topic of Agile approaches and sculpted Disciplined Agile. (DA) into 2012 A year later, which was bought with PMI guts. (Project Management Institute) into 2019. PMI further tried to close its lag in flexible approaches with the help of this toolkit. The story of Disciplined Agile I've already told you. told earlier.
#Processes #Management #Agile #Leadership #Software