#Smart #Business is #Smarter not locating to a #SmartCity

Lets not building Smart Cities, lets Live Smart instead

Just as humanity is starting to deal with business processes that should never have been digitized we might also consider the huge waste in making Smart Cities when we no longer need cities.

Watching humanity evolve in retrospect it is easy to spot the errors and poor judgement, but humanity is on the cusp of a revolution so profound it calls into question the structure of our societies.

Why do we need Cities?

Think for a moment, why do we need cities? They create centralization of people and resources however they also drive costs as often space is insufficient for demand. There is a huge dependency on the need for workspace, shops and local living accommodation.

In a Smart Economy with people engaged in Smart Living people rely on digital communications not face to face engagements. Unless direct physical contact with another person is required for your job you don’t need to be physically present. Most work can be distributed to multiple locations across the planet. Even specialist surgeons can now work remotely and have been doing so for some time, even surgery can now be done through a physical / virtual interface.

What about the time of Day?

Time is a construct, instead on narrow thinking around working day, working time is more productive.

Preparation for Smart Business

The assertion “Lets not building Smart Cities, lets Live Smart instead” is completely correct however the preparation to deal with this change and timeline are another matter. There is also geographies and infrastructure to consider.

Working from Home

Corporations who are already seeking to reduce or remove their huge overheads and dependency upon city office space are offering their staff the ability to work from home and have done for some time. The natural extension to this is the end to centralization completely. This represents a complex issue for Enterprises as they also tend to have large property portfolios maintained in their Enterprise Treasury Assets. While divestment strategies are being established, there are huge risks for those who have not understood that over time the resell value will crash, making city office property worthless.

Working from the World

There are significant problems in the structuring of the world due to notions of status, long held wealth and existing infrastructure. Working from the world will be a lot harder than working from countries that have large investments in infrastructure, hence cities will still exist, becoming an indication of old thinking and technology poverty.

Summary

The cost of creating Smart Cities is huge and relates to infrastructure for jobs and services that won’t be required in the mid term, they will not make a profit and may even not cover their cost of creation and installation. The Smart solution is a distributed model not a centralized one. Creating these types of services takes a huge investment and without the confirmation of a captive customer base, it should be interesting to see how capital can be raised and who will take this risk.

Tagged : / / / / / / /

#UX and #Development cannot exist in the same #Agile workstream

“UX and Development cannot exist in the same Agile workstream” might sound like an outlandish claim but if you fully understand, it’s obvious. Forcing things to work as with the picture above is not a good idea.

Can UX be Agile yes, of course in so far that all the effort and artefacts required to deliver UX can exist in an Agile UX workstream.

UX includes user research, user requirement, KPI’s, system-wide taskflows, concepts, concept testing, persona definition, user roles, user journeys, usability and accessibility standards, sitemaps, key pathway wireframes.

Development can also be Agile, but not all of it, infrastructure and front end need to be in separate workstreams.

The simple way to express this is to talk through backlog items in a greenfield system;

The user can login…..

  • UX will take days
  • Front end will take weeks
  • Back end will take months

The problem is not size it’s Trajectory and Dependencies;

  • UX = T small, understood activity : D access to target audience to validate success and failure paths
  • Fe = T mid, may need investigation : D access to dummy credentials store
  • Be = T long, will require architecture to respond to scalability and bandwidth changes : D modelling data, server set up, pen testing

Once there is a fuller understanding of these very different aspects of defining, designing, building and deploying it’s become clear that these areas have common points but cannot be run together as and Agile project and to tell client’s that they are is not true.

Agilists don’t call this blind behaviour Agile, we call it Fragile (When Agile becomes Fragile nobody Wins) as we know it will shatter at the first problem.

Tagged : / / / / / / / / / /