Kanban and Scrum are popular work methods, especially in development, that are often considered project management methodologies.
I understand that many of you are interested in implementing Kanban or Scrum in our work. That’s why I thought I’d send you a little more information about what each one is.
To begin with, both Kanban and Scrum are oriented toward completing smaller-volume tasks, which in turn aims to lead to increased efficiency.
Table of Contents
Scrum
Scrum uses agile patterns to solve adaptive problems. It has sprints and roles. Scrum is oriented towards personality, it’s better structuring, qualities, and relationships. It is designed for projects where new work requirements are constantly emerging and where we need to be flexible. Scrum allows the insertion of extraneous tasks that, in the judgment of the team, will not interfere with the ultimate goal – providing a higher value for the final product.
How does Scrum work?
Scrum encourages attempts to search and test different ways to be more efficient. Of course, this requires regular checks on work effort and results. That way, the team can quickly identify obstacles and overcome them together. This adaptability to changing requirements is key to achieving greater value, which is the goal. Reference: “Scrum and Kanban: Differences and Similarities“, https://www.powerhp.net/scrum-and-kanban-differences-and-similarities/
Kanban
Kanban is a method of planning and managing tasks by visualizing them. A major difference from Scrum is that the number of tasks here is limited and we cannot insert additional ones if the preset limit is already filled. Adding a new task can only be done after freeing up space for a new one. The purpose of Kanban is to limit work in progress and increase efficiency.
How does Kanban work?
Kanban is based on the principle that reducing and limiting the tasks a team is working on should focus the work, reduce the potential number of defects/errors and reduce distractions. This, in turn, leads to an increase in their productivity. More on the topic: https://www.kievpress.info/differences-between-scrum-and-kanban-agile/
In my opinion, the implementation of Scrum would greatly help in the development of our company.
Through Scrum, we will have the opportunity to receive regular feedback from the end customer, based on which we can further adapt our processes and products. This will increase their value. Scrum enables us to adapt more quickly to the changing environment, reducing risk. And in our business, you know, it’s key to be able to adapt to change if we want to be competitive and successful.
Actual work on the project after defining the project management methodology
Marketing department
Expectations:
To carry out a marketing study to establish and determine and submit a report on the following points:
Is there a consumer need in the market for a specific type of product, based on its unique characteristics.
Possibility of direct competition with another similar product on the market.
Price positioning of the product, concerning the expectations and needs of the market.
To collect the best price-quality offers from different factories/contractors
To determine the potential life cycle of the product in an exemplary long-term plan, as well as to create a business model for the product. Reference: https://www.policymatters.net/scrum-and-kanban-similarities-and-differences/
The time needed to complete the tasks – within three working weeks.
Design department:
Expectations:
To prepare a complete design of the product
Product vision.
Branding and packaging.
Sample QR code creation for customer convenience/instructions for use/.
Technical characteristics and documentation, according to the individual characteristics of the product and according to the individual requirements of the contracting authority.
Resources/parts required to assemble the product.
Development activity
Expectations:
To provide information on whether all required parts for the project can be provided in-house or need to be sourced from external suppliers.
If possible, make a valuation of the parts for the overall performance of the product.
They provide information – does the company have the resources – people and equipment to ensure the implementation of the innovations.
To determine if special training of personnel is required, when assembling the product, taking into account the new technologies of the product, in case there is an outside contractor.
To provide information on additional actions and checks regarding the use of the product / remote access management /
Telecoms – After providing basic information from the Development department, a request for quotation from several telecoms should be made for the price and support of a service, according to estimated quantities of the product.
To realize the product from a drawing to a final product – creating a model.
To establish the quality of the product and to establish in a test environment – the service life of the product at maximum load phases.
Estimated time to complete tasks 4 weeks.
Logistics
Expectations:
Selection of the project contractor – in case the product will be realized outside our company.
Estimating the delivery of specific parts and components to a contractor includes an estimate of price and delivery time.
To collect the best offers regarding the transportation of the product after its realization, to the final point of delivery – the customer’s warehouse.
Provision of customs department in case of importation of goods into the country.
Expected time for implementation of inspections 1 week, after completion of work of all the above departments and approval for action received from the project manager.
Formation of a project team
I am committed to getting to know the project in even more detail as soon as possible, and at the same time, I will be actively involved in the work on the transmission. During the time we are handing over the project, I will have the opportunity to get to know the culture of the company and all the necessary details for my quick adaptation.
At the same time, and to be more effective in handing over the project or for future projects, I ask that we hold a meeting to specify the scope of the project, the communication plans, and all the steps and processes in classic project management. I want this from you because I notice that colleagues are mostly programmers and marketing specialists with whom I think you will be able to deliver the project on time, but since I have experience in project management I suggest and I know that to be sure of the quality of the final product, we also need other competencies and skills.
Please do not under any circumstances take what I wrote with alarm. Since the company has been successfully managing the implementation of projects and they have been successfully handed over, we will do it now with the difference that this time I am offering you something that will help all colleagues working on the project and not only. I am here to “add up” to the built team and contribute my experience.
Let me tell you why we need to add classic project management practices:
You need a diverse group of people who help each other. There will be those who stand out for their social skills, those who stand out for their creativity, and those for their technical precision. And everyone must be able to join their efforts and project them towards the common goal. Sharing the work ethic and vision are the points that need to come together between them and with you as the project director, for the following profiles:
A leader
It is a visionary, with the ability to see the project as a whole, from start to finish. His job is to create a productive work environment by using his communication skills and empathy, but also firmness. The experience and respect earned will help guide and motivate the team, while the positive feedback it provides will push them toward goals.
Control and Quality Manager
His primary responsibility is to ensure the delivery of products or services following specifications to satisfy customers or stakeholders. The project quality manager is responsible for overseeing the implementation process of an organization’s project quality management plan. Reference: “Quality control and quality assurance in Project Management and Agile practices“, https://scrumtime.org/quality-control-and-quality-assurance-project-management-agile-practices/
Realist
It deals with the prevention of risk or problems and the search for solutions that avoid them or minimize the impact of their consequences.
Developer Lead: is the one who captures the vision of the project and makes it their own, identifying all the different ways to make it a reality. Although he is on the same level as the leader in terms of his understanding of the goals and the overall vision, he differs from him with a greater focus on the practical aspects. One of his missions is to ensure that everyone plays an important role in the project.
Communicator
His talent for communication makes him stand out and he always acts as a facilitator, encouraging an open dialogue that ultimately helps promote transparency and agreement. He is a receptive and approachable person, a connected team member who is essential in keeping the team on track and facilitating the transfer of ideas and messages.
Dedicated experts
They are dedicated, believe in what they do, and know how to do it well. It is important to keep these people motivated, especially through feedback and minimizing criticism; and always provide instructions that are as clear as possible.
Manager
Responsible for giving structure to ideas and making them real and practical. In addition, it updates the strategies so that they adapt to the necessary decisions at any time.
This is just part of the journey a project takes and I suggest we start implementing them gradually from here on out and these same practices blend into the company culture.
