Any business development starts with process organization. Before starting a new business or expanding an existing business, we need to have clearly defined processes and a clear understanding of these processes. If we don’t, we will only increase the chaos. We even risk destroying any good assets which we have, including our relationships with customers. If we are just starting our business, we are also going to need a clear understanding of which processes we will need.
It does not matter how many people there are. If there are a lot of people and departments, then processes will be distributed among the departments and people. If there are not enough people, each person will need to perform more functions, and we will know what people we need based on the number and types of functions. In a startup, often one person wears many hats.
So what would we do first?
According to the guide ISO 9001, businesses are divided into the following process groups:
The processes in the first group and the third group are almost the same for different businesses.
The Management processes are the activity of creating the strategy and forming the development direction, management model and principles.
This first group includes the following processes:
1) Strategic Management;
2) Quality Management;
3) Organization Management;
4) Contractor Management;
5) Customer Management;
6) Partner Management;
7) Public Relations Management;
8) Financial Planning and Budgeting.
The main processes are the activities directly assumed by the charter company documents and forming the main product for the market/society.
How would we know these main processes?
The main processes depend on what kind of business you have.
At the beginning we need the clear understanding your goal. After that we have to formulate the main tasks which you will want decide to reach your goal.
So, we know our main processes.
Auxiliary/supporting processes are activities, which are necessary to support the main processes, to form a single platform and typical rules of the unit and processes interaction within all other processes.
This third group includes the following processes:
1) Regulatory Information Management;
2) Project Management;
3) Information Technology and Security Management;
4) Workflow Document Management;
5) Archive Documents storage;
6) Stuff Management;
7) Transportation Management;
8) Administrative Management
9) Supply Chain Management.
When we know our processes we have to describe their inputs and outputs. Process inputs and outputs can be material, financial and information. Each business has own inputs and outputs.
If we only create a company, we describe our company model. If we already have a company, we also describe the model, in this case we don't need to think about our current structure when you make description, we have to think about your goals and tasks for reaching these goals. When we will get the model we can compare our current processes and our model, we will see what we have and what we have not. After process description, we can write the plan for transfer from the current processes to the model processes.
Information about the process description will be in the next article.
I'll always glad to get your feed back and questions.
We know that IT system development is not only about the offer of automation services based on the requirements of the customer or consumers, but it’s about development business strategy, about business development.
For example, you have a shop, and when you created a web-site you have received a new market. If you are working in an international company which work with delivery shipments and you have created new technology about exchanges of shipment dates for your client, a big international company, you get a new market too, your business had gone to the next level because of the new technology. The new technology may give you possibility for work faster, with high quality and with new clients. And all of these examples about development both strategies: IT Strategy and Business strategy.
So, we need successful business analysis, including requirements gathering for this process as one of the main it part.
In the Business Analysis for Practitioners: A Practice Guide by PMI  the term Business Analysis is defined as “the application of knowledge, skills, tools, and techniques to:
All of you know how many projects have fails, and these failures being attributed to requirements gathering, it’s almost 70% of all project failures .
How could we realize the right Business Analysis (or discovered requirements) and get the set of the right requirements?
It’s very important to see in the right direction (Figure). For determine problems and identify business needs we have to see around us, to find obvious things, and we have to use some set of rules.
Figure – Discover requirements
For my opinion, there are three most important set of rules.
The first set is about right questions when you try to discover problems and formulate requirements . It is like a 5W1H (Five Ws and One How) method. Answers on these questions are considered basic in information gathering. Therefore, in the business analysis we have also five Why. Here are some typical questions with why:
In addition, of course, you have to remember to choose the right person as an interviewee.
The second set is about requirements management :
And the third set is about result analysis :
In conclusion, to formulate the right requirements is a very complexity task, and there are a lot of information about different methods and tools. Above rules could be fundament in your requirements gathering.
Some of you know how hard could be to fix up with customer (especially in a large company) a lot of documents when they are part of your procurement.
You have to correct them again and again...to have discuss them with a lot of people, which can have some different opinions about the same things, which can have some different interests.
But how could you make this process working quickly?
I have developed a habit over the years of working in consulting to do the following things:
This is easily done when you have professionals in the field of project management, project office, and very difficult when they are not.
But some organizations don't follow project management processes, and they don't have project management professionals, techniques. And what can we see?
I was convinced on own experience, doing projects for two different large organizations. In one of them the specialists have been trained in project management according to PMBOK, the other heard nothing about it. In the first case, it was not difficult to organize the work properly and perform it easily. In the second case, it took some time on the organization of work on the project from the customer, as it was necessary to actually teach the ideology of project management and operation, as well as to overcome resistance and reluctance to change work style. But and one, and in another case, in the end, the process of working on documents was reduced to the mentioned steps.
I'll be glad to get your feedback.
Thank you for reading this.
Success to all of you.
At work I was being asked to say about differencies between Scrum, Kanban and eXtreme Programming. And I'd like to share my thoughts with you.
So, there are different methodologies you can use to manage project.