Introduction to Agile and Scrum
Agile is a set of guiding values and principles that promote an iterative and incremental approach to software development.
Scrum is a specific framework with defined roles, events, and artifacts used to implement Agile principles.
Key Distinction:
Agile ≠ Scrum
Common Clarifications
Deadlines: Agile works well with deadlines by prioritizing the most valuable work first.
Company Size: Agile is suitable for organizations of all sizes.
Nature: Agile is not a methodology; it is a mindset based on values and principles.
Scrum Roles (The Scrum Team)
A Scrum Team typically consists of 5–9 people working together to deliver product increments.
Product Owner
Responsible for maximizing the value of the product.
Key responsibilities:
Managing and ordering the Product Backlog
Defining product vision and market strategy
Engaging stakeholders
Creating release plans
Ensuring return on investment (ROI)
Scrum Master
Acts as a coach and mentor
Ensures Scrum is understood and properly followed
Helps remove impediments and supports the team
Development Team
Responsible for delivering a “Done,” potentially releasable increment each Sprint
Cross-functional and self-organizing
Includes roles such as Developers, QA/Testers, and UX/UI Designers
Work Hierarchy: Epics, User Stories, and Tasks
Work is broken down into smaller pieces for better planning and execution.
Initiative: High-level business objective
Epic: A large body of work with a shared goal
Example: Create User ProfileUser Story: A short description of functionality from the user’s perspective
Format:
As a [user], I want [feature] so that [benefit].Task: The smallest unit of work derived from a user story
Example: Validate email and password
Estimation
Used to understand effort and complexity
Commonly done using time-based estimates or story points
Scrum Artifacts
Scrum artifacts are information radiators that provide transparency and shared understanding.
Product Backlog
A prioritized list of everything needed in the product
Continuously updated
High-priority items are detailed and refined
Low-priority items are larger and less detailed (often Epics)
Sprint Backlog
Items selected from the Product Backlog for the current Sprint
Includes a plan for delivering those items
Increment
The sum of all completed Product Backlog items in a Sprint
Includes value from all previous increments
Must meet the Definition of Done
The Sprint and Mandatory Events
A Sprint is a fixed time-box (usually 2–4 weeks) during which a usable product increment is created.
Mandatory Scrum Events
Sprint Planning
Entire team defines the Sprint Goal
Selects Product Backlog items to work on
Daily Scrum
15-minute daily meeting for the Development Team
Inspects progress toward the Sprint GoalSprint Review
Demonstration of the potentially shippable incrementStakeholders provide feedback
Sprint Retrospective
Focuses on process improvement
Team identifies actions to improve the next Sprint
Sprint Rules
No changes that endanger the Sprint Goal
Quality standards do not decrease
Scope may be clarified and renegotiated with the Product Owner
Product Backlog Refinement
An ongoing activity to keep the Product Backlog relevant and clear.
Includes:
Adding new backlog items
Deleting items no longer needed
Breaking large items into smaller ones
Reordering or replacing items based on new priorities
Adding estimates and details
Agile 2.0 in ServiceNow
Agile 2.0 Plugin in ServiceNow
Agile Roles in ServiceNow:Product Owner,Scrum Master,Scrum Admin,Scrum userCreating a Product
A Product represents the application or se
Product Name , Description , Product OwnerAgile Group Creation
An Agile Group represents a Scrum team working on a product.
Agile Group Name ,Product , Group Type (Agile Team) , Scrum Master , DeveploerProduct Backlog in ServiceNow
The Product Backlog is a prioritized list of all work items for a product.
Epic
An Epic is a large body of work with a common objective. It can span multiple sprints and is broken down into user stories.Epic Name ,Product, Agile Group, Epic Owner ,Description/Goal
User Story
A User Story is a small, user-focused feature that delivers value.
Story Name / Short Description ,Product ,Epic ,Agile Group ,Story Points / Estimate ,Priority ,Assigned To: Developer ,Acceptance CriteriaSprint
A Sprint is a fixed time-box where work is completed. Agile Group ,Start Date & End Date ,Sprint Goal
-
Sprint Planning
A Sprint is a time-boxed period (2–4 weeks) where the team delivers a potentially shippable product increment.
Tracking Progress
Once the sprint starts, tracking is done via Boards, Backlog, and Reports.
Draft – Work item created but not ready for development; high-level details are added. → Next: Ready
Ready – Fully defined item with description, acceptance criteria, and estimates; ready for sprint planning. → Next: Work in Progress
Work In Progress – Development has started; coding and initial tests are in progress. → Next: Ready for Testing
Ready for Testing – Development complete, awaiting QA/Tester validation. → Next: Testing
Testing – Item is being verified against acceptance criteria; defects logged if any. → Next: Complete or Back to Work in Progress
Complete (Done) – Item meets all requirements, tested, and accepted; included in Sprint Increment.
Cancelled – Item is no longer needed; removed from backlog but kept for traceability.
Draft → Ready → Work In Progress → Ready for Testing → Testing → Complete
↘
Cancelled
If you found this article useful, please mark it as Helpful. It helps others find the content more easily👍🙂
-
Hi @Prathmeshdagade,
I have read your post and I must ask you - can you vouch for the content you just shared?
Some parts of your text don't seem to be your original thoughts. If AI tool was used to generate or rewrite content from other sources, it's important to state that and source the original authorship.
One of the images used is taken from another blog without crediting the authors. This situation is considered plagiarism and doesn't align with principles of intellectual property.
I cannot share the link because it's external link and my post wouldn't be published, but I believe that this screenshot is sufficient to prove it.
The screenshots are from 2019, which makes me think that they are not yours either... or you took screenshots then waited for 5 years to post them? Why don't you add current screenshots? ServiceNow has changed a lot since that and perhaps it would be more relevant to share it from the workspace.
EDIT: And another screenshot is from 2021 - inconsistent to add screenshots from 2019 and 2021:
Also you duplicated the post:
Please, next time before you post something, be sure that you are following ServiceNow Community Code of Conduct for all members.
Do you really think that posting unvalidated content or taking credits of somebody else is helpful for the Community? Wouldn't it be better to select something you learnt and share that particular thing? Something from your own experience? Could you possibly edit your post to contain your real contribution or eventualy state the original sources? What do you reckon?
