--- sourceDocument: Australia Strategic Portfolio Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-business-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia Strategic Portfolio Management ft:clusterId : - itbm bundleId : - itbm workflow : - Technology --- # Agile Development process flow # Agile Development process flow {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Agile Development process flow This Agile Development 2.0 process flow guides ServiceNow customers through managing product development efforts, including product creation, sprint tracking, and release management. It reflects common practices using Agile Development 2.0 application features but allows for process customization to fit organizational needs. Show full answer Show less ## Key Features * **Define Products:** Organize work around products, each with an owner responsible for managing epics and stories linked to business goals (themes). * **Create Epics and Stories:** Break down high-level product requirements (epics) into manageable stories, associating them to products for clear tracking. * **Create Releases:** Set fixed time frames (start and end dates) for delivering products, typically following quarterly or biannual schedules. Associate products, epics, and stories to releases. * **Personalized Backlogs:** Customize backlogs with filters to combine different work items like stories, defects, and incidents, supporting tailored work views. * **Assignment Groups:** Define groups by adding members and assigning story points each can complete per sprint, establishing group capacity based on total points. * **Create and Plan Sprints:** Define sprint durations (usually 1-4 weeks) within release dates. Plan sprint scope by selecting prioritized stories matching team capacity, using velocity reports for estimation. * **Track Sprint Progress:** Scrum masters facilitate daily standups, manage blockers, and monitor story completion. Agile 2.0 dashboards provide burnup, burndown, and cumulative flow charts to visualize progress and workflow. * **Track Release Progress:** Product owners monitor release completion pace against goals with Agile 2.0 Release dashboards using burnup, burndown, and cycle time charts. ## Key Outcomes * Efficiently organize and manage product development work aligned with business objectives. * Enable predictable sprint planning through capacity and velocity insights. * Maintain transparency and control over sprint and release progress with real-time dashboards and reports. * Support flexible adaptation to changing priorities while maintaining collaboration among product owners, scrum masters, and teams. Learn the process that is used to manage product development efforts in Agile Development 2.0, such as creating a product or tracking a sprint or release. Note: The flow explained here represents the common practice for managing agile development efforts using the functionality available in the Agile Development 2.0 application. This flow does not represent the only possible process. Define products : A product can be a set of features or functionality offered to users. Each product can have an owner that maintains the work pipeline, such as epics and stories, for the product. These work items can be associated to a theme, which is related with a business goal. See [Create a product in Agile Development 2.0](https://servicenow-prod.fluidtopics.net/kd9DtjeWV7FMq35K40MjDA "Create a product to represent a feature or functionality important to customers. A product can contain themes, epics, and stories that describe these enhancements from the perspective of a user."). Create epics and stories : Epics contain high-level requirements for your products, which you can use to break down into manageable stories. While creating epics and stories in Agile Development 2.0, you can associate them with a product. See [Create an epic in Agile Development 2.0](https://servicenow-prod.fluidtopics.net/9roFC1xeTsZagxAuPL44zA "Define the high-level requirements of the features that you want to develop by creating epics in Agile Development 2.0.") and [Create a story in Agile Development 2.0](https://servicenow-prod.fluidtopics.net/TM~FNrxNch0G_cXwh~T4IA "Create high-level definitions of your requirements in the form of stories in Agile Development 2.0. Manage and track your stories by associating them to a product, project, or release and by assigning them to an assignment group."). Create releases : Some organizations have a fixed time frame to make their products available to the market, which is referred to as a release. A release has a start and end date, during which several development iterations are completed. For example, you can have quarterly or half-yearly schedules to release new applications or enhancements to existing applications. After you create a release in Agile Development 2.0, you can associate products, epics, and stories to it. See [Create a release in Agile Development 2.0](https://servicenow-prod.fluidtopics.net/AgdGginVuV1FbczAv5395A "Create a release to start associating the stories and scrum tasks of your product development to the release in Agile Development 2.0."). Create personalized backlogs : A personalized backlog can be created by defining filter criteria. For example, one personalized backlog can be a combination of stories, defects, and incidents while the other personalized backlog can be a combination of stories and incidents. In this way, you can create as many personalized backlogs as necessary. See [Create a personalized backlog in Agile Development 2.0](https://servicenow-prod.fluidtopics.net/qiR18UF7JIH9xh5bxVeiEg "Create filters to define which stories appear in your backlog in Agile Development 2.0.") Create assignment groups : Create an assignment group add members to it. For each group member, define the number of story points that they can complete in a sprint. At the group level, the sum of the story points of all the group members determines the group capacity. See [Create an assignment group in Agile Development 2.0](https://servicenow-prod.fluidtopics.net/it4IjZRHlxEuvvbWJy8~Kw#create-an-agile-group "Create an assignment group of the type Agile Team so that you can assign these groups to a product or a release.") Create sprints : A sprint is the time frame in which the development team delivers one or more stories. A sprint can be of any length, but typically takes between one and four weeks to finish. The scrum master creates the number of sprints required for the group, and these sprints are used by the group members to complete the work required for an upcoming release. However, all sprints within a release must be within the release start and end dates. Plan sprint activities : Before a sprint starts, the group and scrum master decide on what stories from the backlog they can commit to complete within a sprint. Stories for a sprint can be selected based on priority. The scrum master must ensure that the effort (total story points) required to complete the stories matches the capacity of the group. While planning your sprints, you can use the velocity reports as guidance to estimate how much work the group can complete in the next sprint. The [Agile 2.0 Team dashboard](https://servicenow-prod.fluidtopics.net/C5TrOjIMHIBFfBePDXOmOQ "Team Dashboard provides a visualization of the team's progress on stories over a given period. It provides team predictability charts and helps you plan the team's capacity for the upcoming sprints. In addition, it provides details of all the team members.") provides Velocity history report and Velocity by type report. * Velocity History: Gain an insight on the overall velocity of the team for the past 10 sprints. Analyze if the team is achieving a stable, predictable velocity, and is meeting the commitments. * Velocity by Type: Analyze the way your team's velocity changes over time and compare the team's strategic workload with operational or other types of workload. {#agile-development-process-flow__ul_mkg_tcj_ntb} For more information on how to plan your sprints, see [Plan your sprint activities in Agile Development 2.0](https://servicenow-prod.fluidtopics.net/MvC3DHylM7s1PkLMSEqDeA "Streamline your sprint activities such as creating, editing, and completing sprints, or adding stories to sprints, using the Sprint Planning tab of the Agile board."). Track sprint progress : The scrum master manages the sprint team efforts, provides progress reports, and removes any blockers that the team encounters. Team members update story records and conduct daily standup meetings to discuss their progress and communicate the concerns to the scrum master and product owners. The team is expected to complete all the stories that are committed for a sprint. The scrum master expects that the stories are fully tested and are ready for release, according to the acceptance criteria. Ideally, the committed stories and the scope for a specific sprint should not change while the sprint is in progress. Agile Development 2.0 provides the flexibility to update as necessary and adapt to changing priorities. However, stories must be added or removed from a sprint only after a discussion between the group, scrum master, and product owner. You can use the [Agile 2.0 Sprint dashboard](https://servicenow-prod.fluidtopics.net/nZ4jSg2R639B1bBrTTuhXQ "Track the progress of your stories in the current sprint and forecast sprint completion using the Sprint Dashboard.") with reports such as burnup and burndown charts to track the progress of the team for a sprint. Tip: If you're running a hybrid or traditional project delivery, you can still use the Agile 2.0 Sprint dashboard to track workflow state transitions using the cumulative flow diagram. For more information about enabling dashboard access, see [Performance Analytics Content Pack for Agile 2.0](https://servicenow-prod.fluidtopics.net/V73dRvWRCa8If2KTHs_TUA "Improve your Agile processes and practices using preconfigured dashboards with data visualizations from the Platform Analytics Content Pack for Agile 2.0."). Track release progress : The product owner tracks the progress of the release and verifies whether the team is completing stories in the pace that is necessary to achieve the release goal. You can use the [Agile 2.0 Release dashboard](https://servicenow-prod.fluidtopics.net/Y42IaHOCJngqhcDTcimtQQ "Track the progress of your stories and analyze scope changes in the current release using Agile 2.0 Release Dashboard.") with reports such as burnup, burndown, and cycle time charts to track the progress of the team for a release. Note: All Agile 2.0 dashboards are available with [Performance Analytics Content Pack for Agile 2.0](https://servicenow-prod.fluidtopics.net/V73dRvWRCa8If2KTHs_TUA "Improve your Agile processes and practices using preconfigured dashboards with data visualizations from the Platform Analytics Content Pack for Agile 2.0.").