![]() And if you want agility and the ability to move fast, you need to be able to communicate that vision efficiently too.Īs an industry, we do have the Unified Modelling Language (UML), which is a formal standardised notation for communicating the design of software systems. If you want to ensure that everybody is contributing to the same end-goal, you need to be able to effectively communicate the vision of what it is you are building. In today's world of agile delivery and lean start-ups, some software teams have lost the ability to communicate what it is they are building and it is no surprise that these teams often seem to lack technical leadership, direction and consistency. Although the software development industry has progressed in many ways, we seem to have forgotten some of the good things that these older approaches gave us. Examples include the Rational Unified Process (RUP), Structured Systems Analysis And Design Method (SSADM), the Unified Modelling Language (UML) and so on. If you look back a few years, structured processes and formal notations provided a reference point for both the software design process and how to communicate the resulting designs. Prescribed methods, process frameworks and formal notations Agile approaches talk about moving fast, and this requires good communication, but it is surprising that many teams struggle to effectively communicate the design of their software. I'm not just referring to post-project documentation, this also includes communication during the software development process. As an industry, we've become pretty adept at visualising our software development process over the past few years although it seems we've forgotten how to visualise the actual software that we're building. ![]() ![]() Visualising your software development process is a fantastic way to introduce transparency because anybody can see, at a glance, a high-level snapshot of the current progress. Whether it is physical or virtual, there's likely to be a story wall or Kanban board visualising the work yet to be started, in progress and done. If you are working in an agile software development team at the moment, take a look around at your environment. Simple Sketches for Diagramming your Software Architecture ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |