You are using an outdated browser. Please upgrade your browser to improve your experience
Before we jump into the terms, it is best that you have a basic understanding of Agile. At its most basic form, Agile is a flexible approach to project management.
Made famous in software development in the early 2000s and then adapted by other industries such as marketing and finance, Agile divides a project into smaller and independent sections called ‘sprints’.
Each sprint will last only a few weeks, allowing team members to focus on just a small project section. This micro-focus allows for continued evaluation and adaptation, often impossible in traditional projects. Once a sprint is complete, the team will move on to the next sprint in the project.
Unlike a traditional project where the goals are set out at the beginning, Agile allows for ongoing changes and involvement from management or clients. Not only does this allow for a more collaborative and responsive process, but it also allows for a final product that is closer to the business’s evolving needs.
Even though we speak about Agile as a project management tool, it is a different way of approaching a project. This is why it is essential that you recruit people with the experience and knowledge to lead your Agile project.
Below are some of the most common terms and phrases you will come across in an Agile framework.
A mindset and set of values focusing on people, incremental and iterative steps to deliver value.
A set of four values and twelve principles that guide Agile software development.
The ability to adapt quickly to market changes with innovative solutions.
A framework that helps teams work together, emphasising flexibility and the ability to respond to change.
A method to manage and improve work systems focusing on just-in-time delivery while not overloading the team members.
A set time for a project, usually no more than four weeks, during which a Scrum team works to complete a specific set of tasks from the product backlog.
A concrete stepping stone toward the product goal created in each Sprint.
The Product Backlog items selected for the Sprint, plus a delivery plan.
Integrating code changes into a shared repository frequently, usually with automated testing.
A short, daily meeting for the development team to synchronise activities and create a plan for the next 24 hours.
A Scrum event to plan the work for the upcoming Sprint.
A graphical representation of work left to do versus time in a Sprint.
A visual tool to track the progress of work through various stages of the workflow.
An ordered list of everything that is known to be needed in the product.
Responsible for maximising the value of the product and managing the Product Backlog.
Facilitates Scrum as a servant leader and ensures the team follows Agile practices.
Team members who create the product increment in each Sprint.
A unit of measure for expressing the overall effort required to implement a product backlog item fully.
A measure of the amount of work a team can complete during a single Sprint.
Moving to an Agile way of working is a business transformation that involves cultural and organisational changes, not just changes in project management practices. That transformation starts with the right people. The right project management team can help implement a smooth Agile business transformation process.
Many companies choose to use a specialist business transformation recruitment agency such as ea Change. A specialist business change recruiter will understand what is needed to deliver a successful business transformation and will know the right people for the job, whether you’re looking for interim staff or permanent hires.