Agile and lean thinking are starting to produce good results, not only in the world of start-ups, but also in IT environments in established organisations. But more value can be created, and more waste eliminated, by bringing lean principles to the business and to the business analysis profession. There are lots of great resources available online. In this post, I gathered some material that inspired me.
When you are working in a start-up with a small number of people, you can take decisions quickly, independent of existing products or services, strategies, organisational structures and so on. That’s one of the advantages of being “two kids in a garage”. In theory, you could simulate such an environment in an established organisation. In reality, it proofs difficult to keep corporate interference out of the way.
As technology keeps evolving, the opportunities for making your customers’ lifes better keep growing. Making things easier, faster, simpler, cheaper, or exceeding expectations more regularly, digitalisation makes it possible. Sounds pretty straightforward, but in reality, this proves to be rather challenging. It requires organisations to question their approach and shift from inside-out to outside-in thinking.
Let me share some examples with you.
While spending some time in Rio for facilitating a business case training, I got to see quite a lot of surfers (mostly before work hours, mind you). At the same time, I came across a video about the Samsung Galaxy Surfboard. The video shows a surfboard with a LED display, enabling the surfer to check weather and water conditions, like the frequency of waves, and to receive text messages. It’s a nice example of how technology can be integrated in just about any aspect of our life.
This demonstrates how digital transformation is blending online and offline worlds, or analog and digital worlds, into a single human experience. It shows how technology has become a powerful enabler for improving our lives. But technology still is just that: an enabler.
An important task for any BA is finding out why. Why do we need this project? Why do we need this requirement? Without understanding the why (the rationale), there is a significant risk of building the wrong solution or implementing features in an ineffective way.
Saying no to strategies, projects and requirements, is a quick and fun technique to uncover a stakeholder’s reasoning and increase your understanding of the project and proposed solution.
Business stakeholders want projects to deliver fast. They often come to the project team with a clear view of the solution, expecting a quick start and not leaving much room or time for challenging and proposing alternatives. However, this mind set carries with it an important risk: blindly building the proposed solution does not guarantee business value.