Follow

Agile (Scrum) Solution

Level:
Intended audience:
Solution Store:

Intermediate
Anyone implementing Agile (Scrum)
Click here to access the Agile (Scrum) templates

High performing companies share these characteristics:

  • They build quality into what they do, reducing unplanned work and rework.
  • Include security as an integral part of continuous delivery
  • Work in small batches and deploy frequently
  • Use automated test plans
  • Have a short mean time to recover and low change failure rate
  • Earn a high net promoter score

As part of a goal to become a high performing company, achieve project success by successfully implementing Agile (Scrum) in your organization.

Introduction

Agile is a time bound, iterative way of delivering software (or a business project) that gets individual pieces of functionality fully complete, tested and documented in rapid release cycles, instead of trying to deliver all functionality at once.

Click image to enlarge

Agile Development is a term that can be used for several software development methodologies including Scrum, Extreme programming (XP), Dynamic systems development method (DSDM), Feature-driven development (FDD), Lean software development, Adaptive software development (ASD), Agile Unified Process (AUP), Crystal Clear Methods, Kanban (development) and Scrumban.

These all share a common vision and core values from the Agile Manifesto. Agile methods all focus on empowering people to collaborate and make decisions together quickly and effectively. Benefits include:

* Constant stakeholder engagement
* Better decision-making through rapid feedback loops
* Transparency and clarity
* Enhanced risk management
* Cost savings due to:
* Defined requirements, regularly delivered
* Minimum viable product (MVP)
* Clear priorities and responsibilities
* Reduced Defects
* Team building
* Accelerated time to market

Scrum is the most commonly used agile framework. It provides a highly structured model with clearly defined roles and responsibilities.

Scrum is the most common way to introduce Agile into organizations due to it's simplicity and flexibility. Scrum is a framework for managing a process. The self-managing, cross-functional scrum team is responsible for delivering features incrementally.

There are eight steps to implementing Agile (Scrum):

Step 1: Groundwork
Step 2: Organize the product backlog
Step 3: Estimate the product backlog
Step 4: Sprint planning
Step 5: Organizing the environment
Step 6: Sprint
Step 7: Sprint review
Step 8: Sprint retrospective

Scrum has three roles:

Role Description
Product Owner The Product Owner works with customers, with the business and with the technical teams to understand what is required from the product.

Committed to the success of the product, this role is responsible for prioritising all work.
Scrum Master The ScrumMaster is responsible for supporting the Scrum Team, coaching and guiding them through this process, and removing any impediments blocking their progress.
Scrum Team A scrum team contains as a minimum a single developer assigned to a particular product or project.

A typical team structure may contain a sponsor, a director, stakeholders, development manager, team/tech lead, developers, quality manager, test lead, testers, project manager and technical architect.

The key concepts are:

Backlog

A product backlog is a prioritized list of requirements for the development team to work on. The development team work through the backlog from the top down, pulling in new items with each sprint. A well-prioritized agile backlog improves planning and helps to set expectations.

Technical Debt

Technical Debt exists when in the pursuit of deployable functionality, corners are cut to make deadlines.  For example, these often include requirements on performance, stability, branding, cosmetic, security, documentation and general robustness. Resolving these issues can ensure higher levels of efficiency and improved stability.

Unplanned Work

Unplanned work includes any break/fix work, emergency software deployments and patches, responding to urgent audit documentation requests, and any other work that needs to be done and has not been planned.

Sprint Planning

Sprint planning meetings are a feature of scrum, held at the start of each sprint. Collectively, the scrum team decides what to work on next and how to do it. The output of this meeting is the sprint backlog.

Daily Scrum

Scrum gets it name from the daily meeting where the whole team including the product owner, any actively involved stakeholders, and any other specialists actively involved in the Sprint meet for 15 minutes to cover:

* What is new since the last meeting
* What is the plan before the next meeting
* Are there any hold-ups?

Sprint Review Meeting

At the end of the Sprint, a Sprint Review meeting is held. Review what was delivered in the Sprint and demo the software.

Retrospective

Following the Sprint Review, hold a Sprint Retrospective meeting. The purpose of the Sprint Retrospective is to reflect on how things went during the Sprint. It’s a chance for the team to discuss the Sprint and consider how they could improve things.

Key Benefits

Here are the key benefits of the RequirementONE Agile (Scrum) Solution.

Pre-defined Templates

Models for best practice approaches can be selected from the Solution Store and customized to make them appropriate for your organization. This reduces the risk of errors and kick starts your project

A Single Point of Truth

A central online repository stores each requirement as a record. Updates, comments and meta-data are controlled and tracked individually. This means no open questions about the agreed upon project requirements, or who made which change when.

A Collaborative Platform

The multi-user environment allows administrators control over which users have access to which project components. This means that information is accessible to those who need it in real time, fully secure and auditable.

Dependency Linking

Parent/child or sibling links show critical relationships between requirements, tasks, feedback and issues. This means you can visualize how changes to one project element impacts others.

Reporting

In-line analytics highlight gaps in coverage, traceability of changes and status of implementation efforts

Typical Use Cases

Here is a typical, but not exhaustive, list of roles and associated use cases that would interact with this solution.

Role Use Case
End users
  • Gather stakeholder feedback
Scrum team
  • Prioritize requirements
  • Break requirements into tasks
  • Participate in estimating requirements and tasks
  • Develop tasks and requirements
  • Participate in Daily Scrum
  • Participate in Sprint Reviews
  • Participate in Retrospectives
Scrum master
  • Prioritize requirements
  • Break requirements into tasks
  • Participate in estimating requirements and tasks
  • Manage Daily Scrum
  • Manage Sprint Reviews
  • Manage Retrospectives
  • Manage blockers
Project Owner
  • Prioritize requirements
  • Break requirements into tasks
  • Manage estimating requirements and tasks
  • Participate in Daily Scrum
  • Participate in Sprint Reviews
  • Participate in Retrospectives

 

Templates

These apps and templates are used for the solution.

App Template
Planning
Specification
Questionnaire

Getting started

  1. Select an existing, or create a new project
  2. Click on the Solution Store, and select the Agile (Scrum) templates
  3. Once you have the templates, follow the Implementation plan.

Additional notes

This is a an initial Agile (Scrum) implementation solution. Customize this solution to meet your product development needs.

Related links

Questions or Comments?

Respond to this post if you want to comment on the template or ask the author a question.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk