Tuesday, March 19, 2024

The latest news from the world of project management

How to fail well...

Failure Is the new success. Here are five ways that you can embrace...

5 Skills Needed To...

Why do projects fail? It's a question that invites a lot of interest and...

Embrace the change: Getting...

New IT systems for a growing business can be an exciting prospect and...

Does a Project Manager...

What makes a successful project manager is a combination of their academic abilities,...
HomeGeneral'I pity the...

‘I pity the fool’ that doesn’t value their B.A.

Value your BAOK, the Mr T reference may be wasted on anyone under 30 but in IT Project Management your ‘B.A.’ is as much a key part of the A-Team as B.A. Baracus ever was!

Often, I’ve seen the holder of the role of Business Analyst be the positive difference between success and failure – so why don’t BAs get the credit that they deserve?

In his great ProjectManagement.com article ‘Business Analysts: The Unsung Heroes of Organisational Success’, Michael Wood suggests it may be two-fold, “First, most senior managers don’t understand the value BAs can bring to an organisation in helping it drive strategic initiatives into operational reality. The second is that there aren’t that many great BAs, so they don’t deliver the value that can be realised.”

Reading Michael’s words gives me cause to pause and reflect on my opening statement. While it’s true that I have seen Business Analysts be the positive difference in an IT Project it is also true that some IT Projects have floundered through a lack of BA basics.

It really matters. I have written in the past that, in the next phase of its evolution, IT will no longer ‘merely’ support the business, it will BE the business.

Consider this. “IT must be positioned as a business unit that adds value. A focus on enabling business objectives must be at the forefront of IT’s thinking. The management of multiple service providers in delivering business outcomes will become an increasingly important capability.” (Ovum 2015- ITSM Trends to Watch:).

It’s a powerful argument for Business Analysts to step up but also for businesses to actively encourage best practice. To do that the C-suite has to get its collective head around the potential a great B.A. can deliver.

I’m a huge fan!

World class B.A.s deliver a measurable difference. They are the coordinators of strategic change, delivering the intelligence that course through the veins of successful IT projects, they have a finger on the business case pulse, and like the best chess players, they are several moves ahead of the moment considering the implications of every decision, not just within the confines of an individual IT project but across the whole parent organisation too.

Business Analysts help improve and constantly enhance your IT services and support by helping integrate Service Delivery and IT and business strategy and giving you the intelligence to review the IT cost of running your services. They play an active role in improving the availability, reliability and performance of your Service Delivery. They define scope, identify and liaise with key stakeholders, and provide clear, actionable requirements to implementation teams.

Describing his Business Analyst one Project Leader says, “She’s like a Project octopus with tentacles influencing every aspect of the project, a great Project Manager in her own right, a process expert and strategist but what I really love is that she never comes to me with a problem without first imagining a solution. Her analysis of the data is always spot on and the solutions she designs are always congruent with the project mission and business case.”

So, to be a great Business Analyst do you have to be a bit of an IT octopus?

In Michael Wood’s article, he rather suggests that you do. he lists ‘Strategic Thinker’, ‘Data Model Conceptualizer’, ‘Project Manager’, ‘Business Process Expert’, ‘Applications Requirements Architect’ and ‘Change Facilitator’ among the character traits of world class B.A.s.

It’s quite a lot to ask! Investing in training your Business Analyst talent to excel at any of these disciplines will pay you a healthy return.

To be fair, I regularly see many of these skills (and more) on display from Business Analysts that I work with but if you do find that you’re falling short there are options.

If a lack of business intelligence reporting is hampering effective Programme Management, you can access PM focussed business analysis in the ‘as a Service’ market to give you a competitive edge. Service Delivery Assessments and CMMI based Service Benchmarking can deliver sustained capability improvement and deliver substantive benefits to your organisation.

With the right partner, delivering a business and culturally aligned service, you can benefit from strategic recommendations and prioritised improvement with risk & business impact assessments.

In conclusion, while every organisation should be seeking to encourage in-house Business Analysts to step up and deliver change, in the meantime, You CAN hire in the business analyst octopus that you need.

Related Posts

Continue reading

From ‘a meh thing’ to amazing! How PMaaS can help build innovation into IT Projects

Experience and anecdotal evidence suggest that Bex isn’t alone in seeking a little bit more. In many organisations now, IT project teams feel that the necessary fixed scope, set budgets, tight deadlines, limited resources and defined roles and responsibilities, leave little or no room for experimentation and innovation. The thing is, if you’re getting the results, do you need the added sizzle of innovating? I think that you do.

Every IT project needs a Dale!

This is one of the things I love about Stoneseed, our team, and the culture we have evolved. When we talk about someone behind their back, it’s always positive and hugely complimentary!  If you haven’t yet had the pleasure, Dale Beeton is Stoneseed’s Head of Client Engagement and, as our clients will attest, he is one of those “extra milers” that make a real difference – and not just from a business perspective.

IT Project Management: Nailing know-how, but are we wondering why?

The trainer was explaining the team’s fairly unique binary approach to scrum sprints, which effectively boils down to them having two duration categories – A) one week long and B) three weeks long. The new hire found this interesting and enquired about the reason behind this approach. In her last job, length and number of sprints would be decided at a goal setting meeting, a twelve-week scrum project could have 15–20 Scrum sprints, which could be as short as a handful of days and as long as a month. So, “Why?” seemed a reasonable question but it was met with either blank expressions or an unsatisfactory explanation. The trainer did not know, nobody on the team could answer either.