The sourcing manager’s role can be quite arbitrary and is very important especially in Agile and Scrum practicing ones. Traditionally the role of a manager was boxed into middle management and senior management categories who decided the quantity of work that needs to happen and who or how to go about achieving these desired attributes. So should the procurements manager also be Scrum compliant? Should the PO and the team be a part of the procurement strategy as envisioned in Scrum? And, is there a clash between the SM and sourcing manager’s responsibilities? Let’s explore.
Sourcing Manager Vs Product Owner:
Scrum principles have a clear mandate for the SM, PO and the Scrum team. The PO is responsible to bring clarity between the team and the client. As a PO the job role is definitely about the value of the products and customer needs. It also encompasses the work-prioritization schedules which the team self-organizes and executes. It has little to do with the sourcing of items; third-party vendor development etc and the sourcing manager would do well to remember that work-control is part of the Scrum team’s responsibility and does not need delegation of jobs.
Sourcing Manager Vs SM:
The role of the SM is a multi-tasking sourcing manager in the making. The SM role is designated to develop and enhance the self-organized capacities of the team in producing sellable products quickly. As there is a huge area that envelopes the duties already being executed by the SM the sourcing manager would do well to remember that he bats for the management team. He can build value and enable both the SM and team by removing hurdles, ushering in improvements and practicing Scrum values more diligently. He is the enabler and management’s teacher on Scrum Teams.
The Sourcing Manager’s Role:
As part of the mid-level management team, the sourcing manager would need to keep the complete picture in mind and enable the building of great customer experience, rapid quick-release marketable products, and building capacities in the organization. As you ascend to higher levels it becomes more about strategy-making, enabling decisions, and bettering the organizational key parameters and productivity.
It is important for the sourcing manager to understand that to build organizational capacity upwards from the Scrum team, it is vital to enable horizontal capacity building. The Agile principles also place emphasis on customer collaboration and changes being systemic. This does interfere with the important negotiation of contracts. If the sourcing for technology, and product development enablers are product and project related, it will make perfect sense to allow the Scrum team to decide on sourcing.
How to be an Agile sourcing manager:
In Agile practice on a Scrum framework the collaboration of multiple vendor and requirements, delineating the procurement process, collaboration strategy decisions, maintaining cordial relationships between team and vendors and ensuring loyal vendor and customer experiences are goals for every ideal sourcing manager or/and SM. The Scrum teams are then free to take decisions on delegated work achievement in a self-organized and managed manner as a team.
Vendor selection is crucial in sourcing. If from a third-party the negotiation starts with the PO and the need for finance. Procurement applications like the Source web can be very helpful in sourcing. To place emphasis on quality, timely-deliveries, procurement lead-time, vendor capabilities, site requirements, pricing, and such parameters the reverse auction strategy works very well within the Scrum framework.
The true enabler in sourcing is removing the hurdles in terms of financials to enable the Scrum team to perform optimally. Since Scrum and Agile are best practices, that teach everyone on the team to be multi-purpose, multi-tasking and self-enabling progressive team members one will require even the management to be Agile. The main role the sourcing manager would then be a wee bit of the PO, SM and traditional Manager’s role rolled into one!
Conclusions:
The Scrum team activities do not include procurement and the management would need to ensure sourcing, procurement or contracts specialist to fill the sourcing and procurement void. Thus the sourcing manager is the management’s tight rope walker on a Scrum team who ensures the Agile multiple C’s of collaboration, communication, contribution, and management cordiality.
To learn more about Scrum, Agile and best practices in project management, Imarticus Learning scores high as a reputed training partner. Enroll and use the opportunity to grow yourself.
Tag: agile practice
Being agnostic with agility: Agile transformation
The word Agnostic Agile in IT means the capacity of something to work without “knowing” the essential elements of a framework that it is working inside. The term can allude not exclusively to programming and equipment that is software and hardware, yet additionally to business procedures or practices.
If being an Agile specialist and as an individual who is in charge of Agile transformation, one ought to perceive the significance of being Agnostic with agility at any stage of life. This means that one framework and structure isn’t the appropriate response that ought to be suited to client setting and a more extensive key vision.
We should consider this necessary. The need is to enable clients to achieve the correct level of agility that addresses their issues and reach up to their requirements. The motive of work isn’t to make system lock-ins or to restrict how agility can be connected to the association, regardless of whether at group levels or at scale. But Agnostic Agile as specialists must endeavor to be bosses of their work and art, comprehend and practice no less than two formally settled structures or strategies, maintain a great connection among ourselves as well as other people, and help to support and develop the agile business experts.
Agnostic Agile business analysis is an appearance of these aims, refined concisely into an arrangement of standards. Agile business development is never again an issue. Companies of each stripe, little respect to its size, company or topography, are utilizing this system consistently to motivate applications to showcase all the more rapidly with higher quality to stuff the primary concern.
But the question arises, how does an association plan for progress to Agile advancement and execute it effectively? How can it maintain a strategic distance from the traps and difficulties? In this article, we uncover some Keys for Ensuring Agile Transformation Success.
- To put the client first, to make them self-standing
Put your client’s advantages first, since that is the thing that you have been contracted to do. Help your clients profoundly comprehend the agile outlook, standards, and qualities rather than just structure specifics. By doing this, engage customers to be independent, rather than being dependent.
- To comprehend upsetting limitations and work to evacuate them
Try to know where your client has been trapped and endeavor to evacuate any imperatives that ruin agility. Make your customer happy and satisfied with your work.
- To give a valiant effort, enhancing theory with practical experience
Apply your best accessible information, knowledge, and learning of agile practices as your present capacities permit; such can originate from your involvement or from any systems that best fit a client’s needs.
- To learn, improve and move forward
Share your own insight and knowledge with other individual specialists, serving to improve and enhance agile practices consistently. This comprises giving helpful criticism where and when suitable in the most aware way, with the goal that all may profit for learning and nonstop enhancement.
- To customize agility to context
There is an art to lean, and agile practices that it is worked by observational confirmations, and that passionate knowledge, comprehension of client context, and client development levels may exceed the appropriation of any technique or structure, despite the fact that that strategy or system may be the more agile thing to do.
- Never misguide and to never manipulate
Never misguide your customer by expressing that you know something when you don’t, and never hide and manipulate any decisions or options that could make some way or another advantage to your client.