ServiceNow connector deployment guide

VilMinds Agile/Scrum Card

What Is Agile?
The Agile movement seeks alternatives to traditional project management. Agile approaches help teams respond to unpredictability through incremental, iterative work cadences and empirical feedback. Agilists propose alternatives to waterfall, or traditional sequential development.

What is Scrum?
Scrum is the most popular way of introducing Agility due to its simplicity and flexibility.Scrum emphasizes empirical feedback, team self management, and striving to build properly tested product increments within short iterations.
Tools Used in agile/Scrum project.
JIRA , Rally , Redmine etc.

Agile Overview.
Delivering small piece of functionality within short period of time (Sprint).
Small piece of functionality is considered as User Story.
Product Backlog: Complete product functionality (user stories).
Sprint = Short period, it can be 2 Weeks, 3 Weeks depends on the project.

Agile/Scrum roles:
1) Product Owner – Responsible for writing user stories, acceptance criteria.
2) Scrum Master – Responsible to manage the scrum and sprints
3) Team (Developer, Testers, Architects etc.) – Responsible to implement and deliver the user stories

Agile Ceremonies or Events:

1) Sprint grooming
Occurs only once at beginning of the sprint, More than 1 Hour
Product owner explains each user story and acceptance criteria and clarifies the requirements.
Each user story is estimated according to its complexity and weightage; Story points is the measure for estimation.

Different tools can be used to estimate the user story. Ex, Jira agile poker, planning poker ( etc.

2) Sprint Planning/ sprint Kick off
Occurs only once at beginning of the sprint, More than 1 Hour
Planning user stories for implementation/delivery for a particular sprint according to team capacity.
Some or all the user stories from groomed stories can be planned for the particular sprint.
Sprint Backlog: User stories taken for that particular sprint.

Braking user stories in subtasks:
User stories will be broken down in the sub tasks like below and assigned to the team members.
1) Analysis and understanding user story- 4Hr
2) Design
3) Writing java code
4) Designing user interface
5) Code quality
6) Unit Testing
7) Test Case writing
8) Test case execution
9) Defect tracing
10) Defect Verification
11) Demo

3) Sprint Review/Demo
Occurs only once at end of the sprint , More than 1 Hour.
At the end of the sprint the implemented/tested user stories will be demoed to the product owner.
Demo to the client (Product owner)

4) Sprint Retrospective
Occurs only once at end of the sprint, More than 1 Hour
The sprint retrospective is a meeting facilitated by the ScrumMaster at which the team discusses the just-concluded sprint and determines what could be changed that might make the next sprint more productive.

Three points will be discussed in this meeting.
a) What went well
b) What went wrong
c) Improvement’s

What went right/well wrong Improvement
Sprint demo went well Requirement was not clear Team Sync.

5) Daily Scrum
This is the daily meeting for the particular sprint, 15-20 Minutes.
Team member has to give the status update to the team in following manner.
What I did yesterday, today and if any blocker/dependency.