I really wanted to find out what people out there think about Scrum for a SQL Server Production DBA.
I have seen one article (http://www.sqlservercentral.com/blogs/sqlsandwiches/2011/05/29/can-scrum-work-for-the-dba/) that talks about this, but this is from 2011. There might be things and perspective changes that happened since 2011 to the present 2017 situation.
Here's something that could help you provide you some insight to the type of situations that the production DBA deals with on a usual basis:
1.Schema/Data Promotions from Test Servers to production servers.
2.Monitoring Servers/Databases continuously throughout the day(Checking the server for space, Memory,CPU etc)
3.Backups/Restores/Disaster Recovery Planning and Implementation.
4.Installation/Management/Monitoring/Usage of DBA Tools like Idera, Redgate, Different versions of Visual Studio's/SSMS's etc.
5.Creating/Scheduling/Monitoring Jobs/SSIS packages, SQL Scripts.
6.Sometimes Creation/Deployment of SSIS packages/SSRS reports/SSAS Cubes.
7.Maintenance/Patch Management/Upgrades/Migrations of SQL Servers etc.
How does all of this fall into Scrum and how to deal with it?
Scrum is being implemented as a new thing from the management side and points are being assigned for everything that is being done. 1 point is being equated to 1 hour, 1/2 point is 1/2 hour and so on. So everyday the DBA is being asked what is being done in the daily scrum and lets say a Database is being backed up, the manager(who is also a scrum master) says: All you are doing is setting up the script and letting the backup go. You aren't doing a thing until the backup is done. What should the DBA do? So no points for monitoring the servers/databases since they are a 24*7 job or rather a full 8 hour job for the DBA.
In scrum/sprint, is time really associated with Fibonacci series(0,1,2,3,5,8,13,21 and so on) points associated with time in someway or the other? From what i have learned this is something to do with complexity and never to equate with time, but is that what management does anyway?
But what really is happening in the name of scrum is that, we are being asked to provide the story, estimated/actual points/time for the story, time started, time completed, and details as to what was done to complete the story. Almost the same as this!! (Is Scrum a status report meeting or a developer meeting?)
Is this Agile/Scrum. What is it?
- How Does scrum fit in for the production DBA in this way?
- Are you a DBA that uses scrum?If so, how do you make it work? If not, how do you get around the manager who loves scrum and insists that you be a part of it?