Agile Project Management With Scrum

What is AGILE?

Agile software development refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams.

Agile methods or Agile processes generally promote a disciplined project management process that encourages frequent inspection and adaptation, a leadership philosophy that encourages teamwork, self-organization and accountability, a set of engineering best practices intended to allow for rapid delivery of high-quality software, and a business approach that aligns development with customer needs and company goals.

Agile development refers to any development process that is aligned with the concepts of the Agile Manifesto.

What is Project Management?

Project management, is the application of knowledge, skills, tools, and techniques to project activities to meet the project requirements.

Project management processes fall into five groups:

• Initiating

• Planning

• Executing

• Monitoring and Controlling

• Closing

Project management knowledge draws on ten areas:

• Integration

• Scope

• Time

• Cost

• Quality

• Procurement

• Human resources

• Communications

• Risk management

• Stakeholder management

So we can now say:

Agile project management is a value-driven approach that allows Project Managers to deliver high-priority, high-quality work €“ and look like rock stars to their stakeholders.

It€™s nothing like the plodding, costly and error-prone approach to project management, which has delivered inconsistent results for years. Agile Project Management reduces complexity by breaking down the many-months-long cycle of building requirements for the whole project, building the entire product and then testing to find hundreds of product flaws.

Instead small, usable segments of the software product are specified, developed and tested in manageable, two- to four-week cycles.

Now what is SCRUM?

Scrum is a subset of Agile. It is a lightweight process framework for agile development, and the most widely-used one.

A “process framework” is a particular set of practices that must be followed in order for a process to be consistent with the framework. (For example, the Scrum process framework requires the use of development cycles called Sprints, the XP framework requires pair programming, and so forth.)

“Lightweight” means that the overhead of the process is kept as small as possible, to maximize the amount of productive time available for getting useful work done.

A Scrum process is distinguished from other agile processes by specific concepts and practices, divided into the three categories of Roles, Artifacts, and Time Boxes.

These and other terms used in Scrum are defined below.

Scrum is most often used to manage complex software and product development, using iterative and incremental practices. Scrum significantly increases productivity and reduces time to benefits relative to classic “waterfall” processes.

Scrum processes enable organizations to adjust smoothly to rapidly-changing requirements, and produce a product that meets evolving business goals.

An agile Scrum process benefits the organization by helping it to

• Increase the quality of the deliverable s

• Cope better with change (and expect the changes)

• Provide better estimates while spending less time creating them

• Be more in control of the project schedule and state

What is Agile Project Management Using Scrum?

Scrum project management is a methodology for managing software delivery that comes under the broader umbrella of agile project management. It provides a lightweight process framework that embraces iterative and incremental practices, helping organizations deliver working software more frequently. Projects progress via a series of iterations called sprints; at the end of each sprint the team produces a potentially deliverable product increment.

Understanding the Value of Agile Project Management Using Scrum.

Scrum is a proven and widely adopted method for achieving software agility. By working in short sprints, this iterative cycle can be repeated until enough work items have been completed, the budget is depleted or a deadline arrives.

Project impetus is maintained, and when the project ends Scrum ensures that the most valuable work has been completed.

This contrasts sharply to the more traditional waterfall style approach that fixes the project scope upfront, requiring the extensive creation of requirements, analysis and design documentation before development can get started.

Delays and budget overruns are common, and the failure to prioritize the feature set often results in low quality products that are overloaded with features that the customer/user does not actually require.

How Does Agile Project Management Using Scrum Work?

The Scrum approach to project management enables software development organizations to prioritize the work that matters most and break it down into manageable chunks.

Scrum is about collaborating and communicating both with the people who are doing the work and the people who need the work done. It’s about delivering often and responding to feedback, increasing business value by ensuring that customers get what they actually want.

Shifting from traditional project management approaches to Scrum project management requires an adjustment in terms of the activities that are carried out, the artifacts that are created and the roles within the project team:

What are Activities in Agile Project Management Using Scrum

The main activity in Scrum project management is the Sprint, a time boxed iteration that usually lasts between 1-4 weeks, with the most common sprint length being 2 weeks.

• Sprint Planning Meeting: at the start of each sprint a planning meeting is held to discuss the work that is to be done. The product owner and the team meet to discuss the highest-priority items on the product backlog. Team members figure out how many items they can commit to and then create a sprint backlog, which is a list of the tasks to complete during the sprint.

• Daily scrum or daily standup: each day during the sprint team members share what they worked on the prior day, will work on today, and identify any impediments. Daily scrums serve to synchronize the work of team members as they discuss the work of the sprint. These meetings are time boxed to no more than 15 minutes.

• Sprint Review: at the end of a sprint the team demonstrates the functionality added during the sprint. The goal of this meeting is to get feedback from the product owner and any users or other stakeholders who have been invited to the review.

• Sprint Retrospective: at the end of each sprint the team participates in a retrospective meeting to reflect on the sprint that is ending and identify opportunities to improve in the new sprint.

What are artifacts in Scrum Project Management?

Scrum Project Management requires very few artifacts, concentrating instead on delivering software that produces business value.

The main artifacts in Scrum are:

Product Backlog: this is a complete list of the functionality that remains to be added to the product. The product backlog is prioritized by the product owner so that the team always works on the most valuable features first.

Sprint Backlog: this is a prioritized list of tasks the team needs to complete during the sprint.

Burndown charts: these are used to show the amount of work remaining in a sprint and provide an effective way to determine at a glance whether a sprint is on schedule to have all planned work finished.

What are roles on a Scrum team?

There are three main roles involved in Scrum project management:

• The Product Owner serves as the customer proxy and is responsible for representing the interests of the stakeholders and ensuring that the product backlog remains prioritized.

• The ScrumMaster is responsible for implementing the Scrum. A ScrumMaster differs from a traditional project manager in many key ways, including that the ScrumMaster does not provide day-to-day direction to the team and does not assign tasks to individuals. A key part of this role is to remove impediments or issues that might slow the team down or stop activity that moves the project forward.

• The Team is made up of a cross-functional group of 5-9 members who are responsible for developing the product. Scrum teams are self-organized will all members collectively responsible for getting the work done.

What You Need to Manage a Scrum Project?

Many teams start out using spreadsheets to manage the product backlog and task boards to see and change the state of tasks during the current sprint, often with a whiteboard and sticky notes.

This approach tends to work well for small, co-located teams. However, as the backlog increases and remote members require project visibility many organizations implement a more sophisticated tool to centrally manage projects and enable cross-team collaboration.