AIM Business Driven Data Solutions Logo
Data | Green, Renewable Energy to Fuel Your Company

The Highest Quality, Innovative DevOps using Microsoft and RedGate tools
Agile, Sprint Planning, Point Estimation, Capacity, Burn Down Rate, Daily Scrums, Sprint Review

Azure DevOps

  • Agile
  • Scrum Framework (Azure DevOps)
  • Sprint Planning
  • Point Estimation
  • Planning Poker

  • Burn Down Rate
  • Daily Scrums
  • Sprint Review / Retrospective
  • Capacity
  • Injections

  • Path Design and Definition
  • Power BI Sprint Dashboards
  • Backlog
  • Vision and Scope Document
  • User Stories

As a FREE Bonus, AIM Offers basic DevOps to any data project at no charge!

At the center of all DevOps exists a development team and an operations team that needs to synchronize as if they were just one team. Some teams are centralized in one, or two locations, where others employ the "follow the sun" model. These teams shift members following the rotation of the sun, so that team members located around the planet (USA, China, Russia, Spain) are working the on-call and support during normal business hours, for up to 24 hours a day, for up to 7 days a week.

Once the development team is ready to deploy to production, an Operations team becomes involved with the Development teem. This pairing of the 2 teams (Development and Operations) is beneficial since they both want to achieve the same goal of getting the new development into production successfully.

The process and methodology most commonly accepted today is Agile (Scrum). The Microsoft Azure DevOps has a Scrum process template that can be easily modified. We suggest avoiding the Microsoft process template named Agile as it is not what most commonly consider Agile.

As a Free add-on, AIM will provide basic DevOps mentoring and implementation to the team that will be taking over the knowledge transfer and project hand-off once a solution is provided. In many cases this can be helping the team start using source control with either TFS, or Git. In other cases, we can help the perm team with point estimation and sprint planning and how to incorporate that with daily scrum meetings. However, these basic DevOps (Free Service) does not include continuous integration and Deployment Automation.

Product Backlog Items (PBIs) and Tasks

Product Backlog Items (PBIs)
Can be either Hours or Fibonacci Sequence (Fabrication Scale)

Can be either Hours or Fibonacci Sequence

In most cases a story point uses one of the following scales for sizing:
1, 2, 4, 8, 16


X-Small, Small, Medium, Large, Extra-Large
(known as “T-Shirt Sizing”)


Fibonacci sequence
1, 2, 3, 5, 8, 13, 21

However, it is tough to identify a story from the scales assigned to them. To do that, each team would have to find a baseline story. It does not necessarily need to be the smallest story, but the one that everyone within the team can resonate with. Once a base-line is determined, sizing of all the user stories should be initiated by comparing them against the baseline.

While estimating story points, we assign a point value to each story. Relative values are more important than the raw values. A story that is assigned 2 story points should be twice as much as a story that is assigned 1 story point. It should also be two-thirds of a story that is estimated 3 story points.

For more information, Choose Below: