---
original_url: "https://jace.pro/blog/intake-processes-i-have-seen/"
format: markdown
ai_optimized: true
---

Intake Processes I have Seen- # Intake Processes I have Seen

November 11, 2017 [servicenow](/tags/servicenow/)

  Enable AI AnimationThis is the different team intake processes I’ve seen during my work with ServiceNow.

# [Intake Process](#intake-process)

## [Light Agile](#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](#light-agile-sprint-ceremonies)

CeremoniesFrequencyAttendeesTeam StandupMonday Every WeekDevelopment Team and ManagerTeam StandupWednesday, Thursday Every WeekDevelopment TeamPlanningWednesday Every Other WeekDevelopment Team, Process Owners, Story Requestors### [Light Agile Support Sprint](#light-agile-support-sprint)

ResponsibilitiesFrequencyHandle Incoming incidentsAs neededVerify new story requirementsWhen availableSize new storiesWhen availableSplit large stories into smaller onesWhen availableMove update sets to test and sandboxEvery other TuesdayMove update sets to productionEvery other Wednesday### [Light Agile Development Sprint](#light-agile-development-sprint)

ResponsibilitiesFrequencyAssign Stories to selfWhen availableDevelop FeaturesAll the timeUpdate Story to UAT when doneWhen availablePull in stories if sprint is shortWhen available## [Heavy Agile Process](#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](#heavy-agile-sprint-ceremonies)

CeremoniesFrequencyAttendeesTeam StandupEvery dayDevelopment Team, and Scrum MasterPlanningWednesday Every Third WeekDevelopment Team, Process Owners, and Product OwnerRetrospectiveTuesday Every First WeekDevelopment Team, and Scrum MasterSizingAs neededDevelopment Team, and Product Owner### [Heavy Agile Kanban Group](#heavy-agile-kanban-group)

Product Owner sets importance of incoming work. Each lane or queue can have a predetermined number of items. When I was there were these four lanes:

Ready
- Working
- User Acceptance Testing
- Ready for Release

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

### [Heavy Agile Development Sprint](#heavy-agile-development-sprint)

ResponsibilitiesFrequencyAssign Stories to selfWhen availableDevelop FeaturesAll the timeUpdate Story to UAT when doneWhen available### [Heavy Agile Support and Release Group](#heavy-agile-support-and-release-group)

ResponsibilitiesFrequencyHandle Incoming incidentsAs neededMove update sets to test and sandboxEvery other TuesdayMove update sets to productionEvery other Wednesday
---
[View this page on GitHub](https://github.com/jacebenson/jace.pro/tree/main/./src/posts/2017/2017-11-10-intake.md).

[Intake Processes I have Seen](https://jace.pro/blog/intake-processes-i-have-seen/) [Jace Benson](https://jace.pro) ![Jace Benson](https://jace.pro/icon-512x512.png)

---

*This content is from Jace Benson's ServiceNow and tech blog at jace.pro*
*Original post: https://jace.pro/blog/intake-processes-i-have-seen/*