Intake Process

This is just the different team intake processes I’ve seen during my work with Servicenow.

Intake Process

Light Agile

This process is in use by a team of three developers running two sprints on a two week span. Each member is rotated through the support sprint every third week.

Light Agile Sprint Ceremonies

CeremoniesFreqencyAttendees
Team StandupMonday Every WeekDevelopment Team and Manager
Team StandupWednesday, Thursday Every WeekDevelopment Team
PlanningWednesday Every Other WeekDevelopment Team, Process Owners, Story Requestors

Light Agile Support Sprint

ResponsiblitiesFrequency
Handle Incoming incidentsAs needed
Verify new story requirementsWhen available
Size new storiesWhen available
Split large stories into smaller onesWhen available
Move update sets to test and sandboxEvery other Tuesday
Move update sets to productionEvery other Wednesday

Light Agile Development Sprint

ResponsiblitiesFrequency
Assign Stories to selfWhen available
Develop FeaturesAll the time
Update Story to UAT when doneWhen available
Pull in stories if sprint is shortWhen available

Heavy Agile Process

This process is in use by a team of eight developers running one sprints on a three week span. Two members are rotated through the kanban group every four weeks.

Heavy Agile Sprint Ceremonies

CeremoniesFreqencyAttendees
Team StandupEvery dayDevelopment Team, and Scrum Master
PlanningWednesday Every Third WeekDevelopment Team, Process Owners, and Product Owner
RetrospectiveTuesday Every First WeekDevelopment Team, and Scrum Master
SizingAs neededDevelopment Team, and Product Owner

Heavy Agile Kanban Group

Product Owner sets importance of incoming work. Each lane or queue can only have a predetermined number of items. When I was there it was four. Lanes were as follows;

  • Ready
  • Working
  • User Acceptance Testing
  • Ready for Release

This was to allow the Product Owner more flexibility to get things done outside the Scrum Process and to assist the Release Team.

Heavy Agile Development Sprint

ResponsiblitiesFrequency
Assign Stories to selfWhen available
Develop FeaturesAll the time
Update Story to UAT when doneWhen available

Heavy Agile Support and Release Group

ResponsiblitiesFrequency
Handle Incoming incidentsAs needed
Move update sets to test and sandboxEvery other Tuesday
Move update sets to productionEvery other Wednesday
Avatar
Jace Benson
ServiceNow Developer

ServiceNow is my day job, JAMStack is my passion.

Related

comments powered by Disqus