Project management is the process of supervising the work of a team to achieve all project goals within the given constraints. This information is usually described in project documentation, created at the beginning of the development process. The primary constraints are scope, time and budget. The secondary challenge is to optimize the allocation of necessary inputs and apply them to meet predefined objectives.
Source: Wikipedia
Although project management is a step-by-step process, this does not mean that projects are easily managed using BPMS (Business Process Management System).
Various project management methodologies are used in practice, usually divided into traditional and modern.
The traditional ones are based on a linear (sequential) approach. Among the most popular of these are:
- Waterfall (cascade method) – projects are divided into phases that must be completed before the next ones can begin.
- PMBoK (Project Management Body of Knowledge) – a set of best practices and standards in project management, emphasizing planning, control and risk management.
- PRINCE2 (Projects In Controlled Environments) – a methodology focusing on dividing a project into manageable phases and the flexibility to adapt to different types of projects.
Modern are more flexible and adaptive. Here are some of them:
- Agile – focuses on iterative development and continuous collaboration with stakeholders. Projects are completed in short cycles.
- Scrum – like Agile, divides a project into phases, but focuses on short-term goals and regular evaluation of progress.
- Kanban – a method based on visualization of work; more about it below.
- Lean – focuses on maximizing value while minimizing waste.
- Six Sigma – focuses on improving process quality by eliminating errors and reducing variability.
Kanban
The word “kanban” comes from Japanese and means “visible description,” referring to its original use in production management, where cards (kanbans) were used to indicate the need for materials and other resources. The method was developed by Taiichi Ōno in the 1950s at Toyota as part of the Lean Manufacturing concept.
Today, Kanban is not only still widely used in the production of physical goods, but also in the management of other projects, including, for example, software development. The system allows for effective workflow management by visualizing tasks on kanban boards, making it easy to monitor progress and eliminate bottlenecks.
To easily visualize this methodology, just imagine a whiteboard, or blackboard, or just a wall, which you then divide into three vertical sections (columns) naming them:
To Do – In Progress – Done
On sticky notes you now need to write all the tasks to be done in a given “project”, and then stick them in the To Do column. Now taking up a single task, you need to move it to the column (list) In progress, and after completion to Done.
In this way, everyone who has access to this “wall” knows at what stage each of the tasks of this project is.
In practice, there are many more columns, and information systems allow for significant expansion of capabilities, such as:
- Sharing Tables, lists and tasks
- Adding descriptions
- Creating checklists
- Assigning specific people
- Setting deadlines for completion
- Adding attachments
- Receiving notifications of changes.
Dew-X is also such a system.
