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

Ceremonies Freqency Attendees
Team Standup Monday Every Week Development Team and Manager
Team Standup Wednesday, Thursday Every Week Development Team
Planning Wednesday Every Other Week Development Team, Process Owners, Story Requestors

Light Agile Support Sprint

Responsiblities Frequency
Handle Incoming incidents As needed
Verify new story requirements When available
Size new stories When available
Split large stories into smaller ones When available
Move update sets to test and sandbox Every other Tuesday
Move update sets to production Every other Wednesday

Light Agile Development Sprint

Responsiblities Frequency
Assign Stories to self When available
Develop Features All the time
Update Story to UAT when done When available
Pull in stories if sprint is short When 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

Ceremonies Freqency Attendees
Team Standup Every day Development Team, and Scrum Master
Planning Wednesday Every Third Week Development Team, Process Owners, and Product Owner
Retrospective Tuesday Every First Week Development Team, and Scrum Master
Sizing As needed Development 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

Responsiblities Frequency
Assign Stories to self When available
Develop Features All the time
Update Story to UAT when done When available

Heavy Agile Support and Release Group

Responsiblities Frequency
Handle Incoming incidents As needed
Move update sets to test and sandbox Every other Tuesday
Move update sets to production Every other Wednesday