BPO Technology

Read more

Read more: Agile development

Scrum: A better way to build software

Scrum is an iterative and incremental software development methodology for managing product development. It focuses on building software that meets business needs.

A quick overview of the Scrum framework

  • A product owner creates a prioritised wish list / requirements called a product backlog.
  • During sprint planning, the team pulls a small chunk from the top of that wish list, a sprint backlog, and decides how to implement those pieces.
  • The team has a certain amount of time (a sprint) to complete its work, but it meets each day to assess its progress (daily Scrum).
  • Along the way, the Scrum Master keeps the team focused on its goal.
  • At the end of the sprint, the work should be potentially shippable: ready to hand to a customer, put on a store shelf, or show to a stakeholder.
  • The sprint ends with a sprint review and retrospective.
  • As the next sprint begins, the team chooses another chunk of the product backlog and begins working again.

The cycle repeats until enough items in the product backlog have been completed, the budget is depleted, or a deadline arrives. Which of these milestones marks the end of the work is entirely specific to the project. Scrum ensures that the most valuable work has been completed when the project ends.

Read more: You are the product owner

The product backlog

The product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product. The product owner is responsible for the product backlog, including its content, availability, and ordering.

The Product backlog lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases. Product Backlog items have at least a description, order, estimate and value.

We will maintain the product backlog in an electronic tool (Jira) and provide you access to your project. Here you can view and maintain the product backlog, view the sprint backlog and have insight into the progress of the sprint.

The following is a sample of a product backlog including a defined sprint backlog.

Sprint Backlog

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment.

Read more: Our deliverables, your product

Definition of ‘Done’

When a Product Backlog item or an Increment is described as ‘Done’, everyone must understand what ‘Done’ means. The team has a shared understanding of what it means for work to be complete, to ensure transparency. The Scrum Team uses it to assess when work is complete on the product Increment. The product owner can also be assured that the increment delivered is according to BPO Technology’s standard.

Our standard definition of done includes:

  • The code for the backlog item is completed
  • The code is commented, and checked in current version of source control
  • Peer reviewed (or produced with pair programming) and meets development standards
  • Build has no errors
  • Unit tests written and passing
  • Deployed to system test environment and passed system tests
  • Passed UAT (User Acceptance Testing) and the status updated on the project board
  • Build/deployment/configuration changes implemented, documented &communicated
  • Relevant documentation/diagrams produced and/or updated

Read more: Our talent

Having good talent means taking our responsibility and being a good employer. We take care to be fair and socially responsible towards our talent. We pay above average wages, and for each hour we can book to a client, we will contribute a fixed sum to an employee share fund. This will be distributed evenly among employees irrespective of whether they have worked directly on projects or not.