There is no substitute for drawing out the architecture. Visualisations act as a campfire around which we gather to tell stories (Al Shalloway)ĭrawings can act as a campfire to help your team reach a common understanding. You can read more about it in a great article by Nazzaro and Suscheck over at the Scrum Alliance. Using the INVEST system for user stories can start to form another language that everybody speaks.
It sounds trite but there is no such thing as a stupid question – usually this means that there is some insight missing on the part of the listening, not the asker, because the listener has failed to divine the ‘question behind the question’.įinding a Common Ground – User Oriented Talking Moving Forward with Communication Strategy and Common Tools
This is where the business minds come in. In the real world, translating wish list items into time, money and resources means that priorities can be built, and project dependencies assigned. Can people get what they want technically? If they have enough money, time, resources and perfect skill sets, and the rest of the world stands still whilst they do it – possibly. Money is a language that everybody speaks. There needs to be a brake that asks What is the business value in adding this technical feature? Just because something is technically beautiful doesn’t mean that it is the right path and everyone should shoot down that rabbit hole. This also happens to business people because they don’t have the engineering background, and it’s easy to get sideswiped by detail rather than bigger picture. So, for example, what seems obvious to a hardware person, is completely oblivious to a business person. On the other hand, the business person can bring a hearty dollop of common sense to the proceedings what’s technically correct may not add any business value at all.īusiness first, tools second. The tools should serve the business value if not, we get into the ‘shiny gadget’ syndrome and get very distracted by devices. This requires people from various backgrounds such as engineering, marketing, data science, business leadership….the teams are blended, with a range of skill sets and perspectives and it’s hard to find a common ground. With IoT, we start to talk devices, data, networks, applications, consumer needs, business impact, marketing…. How do we find a common ground for communication and technological understanding to rule the project?Ĭommunication is an issue in just about every project I’ve ever seen. Delivering and running IoT projects has proved the most problematic, however. What’s Technically Beautiful may not make any Business Sense. This blog series is aimed to give you a compass to find your way through it. If you think Business Intelligence projects are hard….
0 kommentar(er)
