Project Management

To hit pay dirt

by
Hi to all of you, and welcome to this blog about management, projects, IT, etc. and about life among all of that. I'd like to share my thoughts, knowledges, experiences and to propose them for discussions.

About this Blog

RSS

Recent Posts

Business processes and project management processes: correlation, integration, evolvement

Interesting research. Who will be next? Would it be possible?

What does a business need first in order to begin growing?

Inspiration interaction

New Year...new digital workplace trends...AI and robots

Categories

Agile, Business Analysis, Business Analysis, Business Processes, Career development, Communication, Information Technology, Integration Management, IT Methodology, IT Strategy, Leadership, OPM, Organisation Project Management, Organizational Management, Organizational Project Management, PMO, Process Management, Project Management, Requirements Management, Requirements Management, Scope Management, Scrum, Strategy, Time Management

Date

What does a business need first in order to begin growing?

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:

  • management processes;
  • main processes;
  • supporting processes.

 

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.

Posted on: April 08, 2019 07:28 AM | Permalink | Comments (11)

New Year...new digital workplace trends...AI and robots

New Year is coming very soon. So…it’s time for taking stocks and for new trends. I think the most important things which has been affected of all people in outgoing year were the artificial intelligence and using robots. A lot of people worry when they see how quickly these things are developing, growing up and see how they could be dangerous for people. 

But for my opinion we have to remember that these thing are only our technologies. Only people can decide how they will use. 

At this point I’d like to mention Antonio Guterres, Secretary General, United Nations, who said, that the main rules in the IT, in the using new technologies are that IT and new technologies must be safety and ethical. He said this in his speech on the Web Summit in Lisbon, November 2018, which called “Nurturing a digital future that is safe and beneficial for all”. I was there, I had listen him and it was really inspiring.

And I completely agree with him. Only if people will use new technologies, including AI and robots, in this way humans will go to next level their development. 

A lot of people feel fear that robots could change the people, but for the now it's not possible. Just look at the example from  China Xinhua News. Their experiment with the robot as a news ancor was fail, because it was not interesting to see the robot, the robot had had a voice and appearance modelled on Zhang Zhao, a real ancor with Xinhua. But a lot of people didn’t like it because there is no emotions, it was some monotonously.  And yesterday I had got the “2019 PMO Predictions: 4 trends for the digital workplace” by changpoint.com.  I see an interesting thing in these trends because they all concern the above problem.

The first trend is “Digital disruption requires new skill set from your people…but remember, they’re only human”. It means higher demand of the soft skills. We can see it now too when people must have not only technical skills, but it’s very important to have the empathy, flexibility, communication skills, emotional intelligence, creativity, the ability to teach other people, etc.   

The second trend is “Digitalization requires an adaptive mindset…and a panoramic view of the landscape”. It means that to have the ability to look at the problem from above, to understand the world processes, to know new technologies, to be flexible for changing the working methods and tools, to think strategically.

The third trend is “Adaptive technology is your friend…and your transformativeally”. It means that we have to enjoy these technologies and find the best using of them in our activities and agile technologies.

The forth trend is “Collaboration…the blending of people skills and digital delivery”. Digital delivery will continue growing up, and it could be very useful in any businesses. 

We can't also deny robot and AI father development and, for my opinion we could find the ways of effectivness collaboration, it will give us a lot of benefits. 

I'd like to propose to listen a talk between Rao Dalio and Garry Kasparov on the Web Summit 2018 “Artificial intelligence is making more and more of our decisions for us. If this capacity limitless or are there some things only human intuition can determine?”

https://youtu.be/KvLsMQPo-Hc

It would be interesting to know your view point. Don't hesitate, leave your comment. Have a nice day and successful stories!

 

Posted on: December 16, 2018 05:38 AM | Permalink | Comments (13)

Scrum vs Kanban vs XP

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. 

  Scrum Kanban XP (eXtreme Programming)
Goal Use of cross-functional, self-organized, and empowered teams who divide
their work into short, concentrated work cycles called Sprints
To alleviate  impediments that cause us to take longer to deliver, not remove necessary pieces of the process. To organize people to produce higher-quality software more productively.
Date of birth In the mid 80’s, Hirotaka Takeuchi and Ikujiro Nonaka defined a flexible and all-inclusive product
development strategy where the development team works as a unit to reach a common goal. Scrum has
increased in popularity and is now the preferred project development methodology for many organizations
globally. 
Kanban developed in the 1940s as a subcomponent of the Toyota Production System and has its origins in these Lean and Just In Time (JIT) manufacturing processes. XP has been created  in 1996 by Kent Beck during his work on the Chrysler Comprehensive Compensation System (C3) payroll project.
Current state The Scrum framework can only be used for small projects. However, it can easily be
scaled for effective use in large projects. 
One of the reasons many groups implement Kanban is to figure out how to deliver more consistently. Kanban, as well as many other methods/processes, is often chosen and implemented by the management or leadership layer and the values and goals are communicated down to developers or other individual contributors. It's a very effective metodology for the small command programmers. Team size should be 5 or less people.
Speciality A key strength of Scrum lies in its use of cross-functional, self-organized, and empowered teams who divide
their work into short, concentrated work cycles called Sprints. Scrum is one of the most popular Agile methodologies. It is an adaptive, iterative, fast, flexible, and effective
methodology designed to deliver significant value quickly and throughout a project. Scrum ensures
transparency in communication and creates an environment of collective accountability and continuous
progress. 
In Kanban the workflow is visualised: work is broken down into small, discrete items and written on a card which is stuck to a board; the board has different columns and as the work progresses through different stages (e.g. ready, in progress, ready for review etc) the card is moved accordingly.
In Kanban the number of items that can be in progress at any one time is strictly limited.
Extreme Programming is successful because it stresses customer satisfaction. Instead of delivering everything you could possibly want on some date far in the future this process delivers the software you need as you need it. Extreme Programming empowers your developers to confidently respond to changing customer requirements, even late in the life cycle.Extreme Programming emphasizes teamwork. Managers, customers, and developers are all equal partners in a collaborative team.
Values 1. Focus
2. Courage
3. Opennes
4. Commitment
5. Respect
1. Transparency
2. Agreement
3. Balance
4. Respect
5. Understanding
6. Leadership
7. Collaboration
8. Customer focus
9. Flow
1. Communication
2. Simplicity
3. Feedback
4. Courage
5. Respect
Principles 1. Roles Guide
2. Empirical Process Control
3. Self-organization
4. Collaboration
5. Value-based Prioritization
1. Start with what you do now
2. Agree to pursue incremental evolutionary change
3. Initially, respect all roles, responsibilities and job titles
The principles that form the basis of XP are based on the values just described and are intended to foster decisions in a system development project. The principles are intended to be more concrete than the values and more easily translated to guidance in a practical situation.
Roles Core Roles:
Product Owner
Scrum Master
Scrum Team
Non-core Roles:
Stakeholders
Scrum Guidance Body
Vendors
Chief Product Owner
Chief Scrum Master
No existing roles. Some teams enlist the help of an agile coach. Tracker, Customer, Programmer, Coach, Manager, Tester. Anyone can be Doomsayer, Gold Owner (may be the same as the Customer)
Key metrics Sprint Velocity (2 weeks) Cycle time Iteration time (2 weeks)
Activities 1. Initiate
2. Plan and Estimate
3. Implement
4. Review and Retrospect
5. Release
1. To Do
2. Development
3. Test
4. Release
5. Done
1. Planning
2. Managing
3. Designing
4. Coding
5. Testing
Practices 1. Planning
2. Daily Scrum
3. Review and retrospective: Sprint Review and Sprint Retrospective
4. Extension: Backlog reinement and Scrum of Scrums
5. Artifacts: Product Backlog, Management, Sprint Backlog, Product Increment, Extensions (Sprint burn-down chart, Release burn-up chart)
1. Visualize
2. Limit Work-in-progress
3. Manage Flow
4. Make management policies explicit
5. Improve collaboratively (using models and the scientific method)
Extreme Programming has 12 practices, grouped into four areas, derived from the best practices of software engineering:
Fine scale feedback:
Pair Programming
Planning Game
Test Driven Development
Continuous process:
Continuous Integration
Design Improvement
Small Releases
Whole Team
Shared understanding:
Coding Standards
Collective Code Ownership
Simple Design
System Metaphor
Programmer welfare:
Sustainable Pace
Change philosophy Teams should strive to not make changes to the sprint forecast during the sprint. Doing so compromises learnings around estimation. Change can happen at any time. A high degree of developer discipline along with continuous customer involvement for the duration of the project. 
Cadence Regular fixed length sprints.  Continuous flow. Iteration.
Release methodology At the end of each sprint if approved by the product owner. Continuous delivery or at the team's discretion. At the end of iteration.

So, there are different methodologies you can use to manage project.
I think the main weakness in all these methodologies is poor knowledge about product. And sometimes we are trying to develop existence products when we need to create new system.
We need to choose methodology or to combine methodology tools in depending from kind of project and its scope. We need to take cognisances of experience, qualifications and conditions.

 

Posted on: October 07, 2016 12:21 AM | Permalink | Comments (13)
ADVERTISEMENTS

"Every child is an artist. The problem is how to remain an artist once he grows up."

- Pablo Picasso

ADVERTISEMENT

Sponsors