business architecture & analysis
Lean and agile have become a thing in most organisations. They have a significant impact on how projects are run. As a consequence, they heavily influence what people expect from business analysis.
But what exactly is lean business analysis? Can and should analysis work be performed in an agile way?
Have you ever been in a situation where stakeholders presented you a solution to analyse and get implemented? Where your devotion to your analysis work uncovered more insights on the real need or root cause, and brought up alternative solutions? Where you have been unable to convince your stakeholders hereof and really influence the project’s focus?
Having impact is not only of direct benefit for your organisation, it’s also important to feel valued for your work.
Many executives admit they struggle with turning their strategy into a business reality. What can business analysis do about it?
So your team is working hard, iterating on your product, getting customer feedback along the way and turning it into a great solution. But are you sure you are going in the right direction?
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.
The BA conference 2016: Transforming Ideas into Action. Far too much inspiration to wrap up in a short blog, but still, here are some of my takeaways.
Sometimes, it only takes twenty seconds of insane courage to get what we want. The courage to simply ask for it. Want to be involved during project initiation and not just execution? Ask. Want to try a new technique or approach your stakeholders are not used to? Do it and see what happens.
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.