What the heck is Scrum, and How Can a ScrumMaster Benefit my ERP Implementation?
Have you heard the term, “scrum” and wondered what it is? Maybe you have; maybe you haven’t, but it’s a term you might become familiar with if you’re implementing a new ERP system…and you’ll be interested in knowing how having a ScrumMaster on the implementation team can be a big benefit.
But first, let’s take a step back and talk about where scrum fits in: The Agile methodology for project management. ArcherPoint believes in Agile values and principles and favors what is called a Scrum framework for ERP implementations. We feel this provides the best methodology and practices for the realities of a complex ERP deployment.
The traditional methodology for ERP implementation projects has been Waterfall. However, Waterfall does not allow for inspection of the product during development and relies heavily on documentation and Single Leader Work Groups, which produce less then desirable results. At ArcherPoint, we seek to maximize the value of our self-organizing teams to provide the highest satisfaction and velocity for our clients through continuous project review, communication, and collaboration from all parties.
Values of the Agile Manifesto
- Individuals and interactions over process and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
How Scrum fits into the Agile methodology
- Scrum is an Agile framework.
- Scrum works because it creates an effective environment to manage uncertainty, risk, and complexity in product development.
- Scrum seeks to provide a product development framework, not a people management framework.
Scrum is based on the following three principles
- Transparency – Process and product visible at all times (News is delivered even if negative)
- Inspection – The process and product are inspected frequently to see how both or either may be improved
- Adaptation – Due to frequent inspection of product and process we can adapt to improve both
Scrum is also based on five core values
- Openness – Environment that is open and people can be honest.
- Courage – People must have courage to speak out in order to adapt and try new things and ideas.
- Focus – This is necessary as the team depends on each other to reach the team goal; the delivery cycle is less in Scrum (planned in sprints with little time for waiting).
- Commitment – People can make commitments to each other based on short periods of time; if they cannot keep their commitments, the whole team suffers.
- Respect – This is required for courage and openness to exist. Respect is provided automatically and everyone must mutually maintain this respect.
There are three Scrum Roles
- Development team:
- Cross functional
- No titles are used
- No sub-teams are used
- Individuals may have specialized skills, but accountability lies within the team
- Team is self-guiding
- Serves the Product Owner, Development Team, and Organization
- Assists in sprint reviews, team planning, removing roadblocks/impediments, coaches Scrum team, facilitates change that increased productivity, communicates with all parties
- Product Owner:
- Collaborates with the team to groom product backlog, provides overall leadership for their company, provides vision, helps team prioritize product backlog, attends meetings with team as needed, provides cross organizational awareness, and provides leadership.
As most projects change and evolve over the lifetime of the project, practicing Agile using Scrum may help to identify project risk earlier and create value for you during your implementation by providing true team velocity. Having client/client teams involved with the planning and review of projects provides insight to projects and their progression at a high level as well as at a task level throughout the course of the project.
If you have additional questions about the agile methodology, scrum, or the best way to implement your system, contact the experts at ArcherPoint.