Business Analysis Training NZ

Recession

How Business Analysts Can Help Companies Survive a Recession

How Business Analysts Can Help Companies Survive a Recession The current financial climate has seen a recession not only in New Zealand but also overseas, leading to companies looking for ways to cut costs, restructure, and even merge to survive. Business analysts can play a crucial role in helping companies during this period by focusing on continuous improvement and business transformation. Continuous improvement involves applying process-level improvements to reduce waste in the organization. Business analysts can help by focusing on reducing waste at the process level, making processes more efficient, and providing clarity to senior leaders about the impact of cost-cutting measures. On the other hand, business transformation involves a top-down approach where a company reflects on its business model and unique value proposition (UVP). Business analysts can assist by reviewing the company’s UVP and identifying areas where fundamental changes can be made. During a recession, companies tend to focus on their UVP, which is what customers come to them for. This may result in turning off services that are not core to the business or not what makes them unique to their target customers. It’s important for businesses to be conservative with their spending and to look for ways to cut costs. However, this can be a difficult time for many people, and it’s important to remember that there are ways to help. Business analysts can use their skills and knowledge to advise friends and family who may be affected by the recession, helping them to identify new career opportunities and navigate the job market. By focusing on continuous improvement and business transformation, business analysts can help companies and individuals survive and thrive during a recession.

How Business Analysts Can Help Companies Survive a Recession Read More »

Programmes

Building a Framework for Living – Building Programmes from Strategy

We have defined our strategic objectives and now we need to look at how we are going to get after them. A lot of big businesses have a project management office that manages the programme of work for the year and have project managers, business analysis and solution architects that collectively work on a project to complete a piece of work. As far as a project owner and/or sponsor is concerned this is a great model and they can define their requirement and get a solution implemented through the solution delivery lifecycle. What is sometimes forgotten when you work on projects is that generally your project is part of a greater programme and what is more commonly missed is that those programmes exist to help achieve a strategic objective. With the structure of corporate being quite hierarchical with multiple department heads wanting to get their project funded the programme of work can get messy very quickly. Linking the Strategy objectives to each programme and then project can help prioritise what is important and what will give the business the biggest bang for buck! In order to keep programme planning simple I am going to take our example from chapter 4 – Just Law and I am going to work down from the Strategic objectives. Be well aware that most companies’ programmes of work are already in flight from the year before and strategic objectives are hardly even linked or used to prioritise one programme against another – this is changing however! In the case of  Just Law we have our 3 strategic objectives which we examined in more detail. To meet SO1 John firstly needs to work out  how he plans to get more clients in the door. For S02 John’s needs a change project to reduce steps in his current sales and purchase management process and finally for S03 johns needs to have a small recruitment project to find and hire the right lawyer. As I have been involved in many projects I would go ahead and state that John will have a programme consisting of at least 3 projects: 1. Investigate the options for increasing client number and implement, Implement a streamline sales and purchase process and recruit a lawyer. Seeing as John wants to increase revenue this year through client number he will use a reserve fund to hire a business analyst who has recruitment skills to help him get after this change programme.

Building a Framework for Living – Building Programmes from Strategy Read More »

Business Entities

From Cells to Intelligent Life – Business Entities

From Cells to Intelligent Life – Business Entities What are these business entities you speak of? Well, these Business Entities’ are things that describe the key groups of information that a business requires to operate. BE’s are nouns and should be tangibles that exist.  Many businesses have an illusion that they are unique or different to other businesses in their field and hence when asked to describe the inner workings of their business they make up terms and use corporate lingo to talk about their operations.  It is up to the analyst to define common best practice terms when modeling the entities of the business – but feel free to use business context aliases in the description to keep the corporate junkies happy. To help understand what these business entities are – let’s look at a few examples: For each example, I will outline a two-sentence description of t he business and then list the business entities as I see them. Joes’ Car Tires sell tires they import from various manufacturers. They have 10 stores they own and operate nationwide. The main business entities of Joe’s Car Tires are the physical things that make up the business at the highest level. In this case: Customers, Manufactures, Staff, Sales, Tiers (Products), Importers, Stores Is that it? Well, if you think you can use the business entities above to store all information about the business, use them to describe the business operations and model all processes against that, yes you are close. Do you get it right all the time? No but take a good stab and go with what you’ve got as you can always add to the list during the modeling process. Now let’s look at a school. Hill High has 50 staff and 500 students and operators in one location. There are no fees to study at Hill High. So, what are the business entities? In this case: Students, Teachers, Subjects, Classes, Rooms, Timetable, Ministry of Education There are a lot of things that could be added to a list that a school may have but primarily the things above can be used to describe the inner workings of any school. Finally, with Just Law we can describe the elements of this one-man lawyer business like this: Client, Case, Lawyer, Fees, Service The trick to business entity modeling is to keep it simple! These are the foundations of the business and everyone in the business should be able to understand what you model. Ok we now have some business entities. What is next? And why are these so important? The next step is relating everything we model to these BE’s. This will help with consistency, verification and will be the core connection between the technical work and the business work.  Let’s take Customer from Joe’s Car Tires: The Customer relates to some of the other entities directly and all the others in-directly. Customer visits a Store Customer chooses tires/project Customer buys/store Sales the Tiers/Product Describing the relationship between the core customer related BE’s above can help paint the base use stories. There may be several additional processes in the customer sale scenarios however the relationship between the BE’s have captured the essence of the customer sales process and more importantly describe the customer sales process for all product based sales companies. Why is it important to relate Joe’s Car Tires to other Sales companies? Well if we can have a consistent model we can start to identify what is common to every sales business and what is unique to that business.

From Cells to Intelligent Life – Business Entities Read More »

Business Context

The Big Bang – Business Context and Environment

Business Context and Environment Working as a contract business analyst for many years now, I have seen my fair share of different size and shaped businesses. As much as I think I have seen it all before there is always something that surprises me when I start working for a new client. Luckily one of the key skills of any Business Analyst is to land on 2 feet no matter what is thrown at them. When I used to interview staff at one of the most “flexible” companies I ever worked for, I would ask the potential business analysts the following question – If you walked into a scoping workshop and asked the sponsor what the objective of their new project was and they answered “Awesome Invoicing” – what would you do? The most common answer I received from skilful applicants was that they would start to work through the current state and ask what would need to happen to make their current invoice an awesome invoice (future state) – i.e. defining awesome. Unfortunately, this situation happened to me on my first day at a new company and no matter what angle I tried or technique I pulled out from my business analysis hat, the best response I was ever going to get from this person was variations of the word “awesome”. A few weeks later I found out the sponsor of the project had previously worked with a large consulting firm who had analysed and predicted huge savings if invoicing was made awesome. The only issue with this report was we now knew what the problems were and how much they were costing the business but had no idea of what the detailed current state was and no analysis or design to resolve these issues. In addition to this piece of business context, I also found out later that this sponsor didn’t think there was any value in going over what they wanted again with a new BA (I had replaced a previous staff member) and all they wanted to do was go straight into talking about delivery. It was clear to me, being the most experienced BA in the company, that business did not know what BA’s did and how they could help. Secondly, being a team in IT meant that whatever method we tried we were allocated once a project started to implement a solution – not defining the outcomes or upfront requirements. Knowing the personalities, environment, financial position and culture of the business you are working for is vital if you wish to gain understanding and insight into the enterprise. This can be vital to maintaining your own existence on a piece of work or at least your integrity. Understanding the specific business context is not mandatory initially but can speed up your analysis and help you gain the respect of the business users you are going to be working with. When first assigned to a specific piece of work it is important to know how your cog affects the machine. We as Business Analysts exist to facilitate, analyse, elicit and translate requirements into solutions but I equally think we are organisms of the enterprise that need to appreciate how our future state changes impact other projects and the business environment not just within our project scope. If we are to do this effectively, we need to define our requirements using the building boxes of any business – in the next blog post we will talk about business entities!

The Big Bang – Business Context and Environment Read More »

Scroll to Top