FSM AGILE –

Training - Rathi
 WHAT IS AGILE?

Agile is a project management methodology that uses

short development cycles called sprints to focus on
continuous improvement in the development of a product
or service.

ProV International
 WHAT IS AGILE?

The idea behind Scrum is not to “do more work,” it’s

to work smarter and thus accomplish more.

ProV International
 TWELVE PRINCIPLES OF AGILE

• Customer Satisfaction
• Welcome Change
• Deliver a Working Software 
• Collaboration 
• Motivation 
• Face-to-face Conversation
• Measure the Progress as per the Working Software 
• Maintain Constant Pace
• Monitoring 
• Simplicity 
• Self-organized Teams 
• Review the Work Regularly
ProV International
 FOUR CEREMONIES OF SCRUM

Sprint Planning Sprint Demo Daily Standup Retrospective

Also known as a
A team planning A sharing meeting A review of what
stand-up, a 15-
meeting that where the team did and didn't go
minute mini-
determines what shows what well with actions
meeting for the
to complete in the they've shipped in to make the next
software team to
coming sprint. that sprint. sprint better.
sync.

ProV International
 DAILY STAND UP

What is Daily Stand-up?

A daily stand-up is a daily status meeting among all team
members, and it is held roughly for 15 minutes.
Every member must answer three important questions −
• What I did yesterday? (with the user story numbers)
• What I'll do today? (with the user story numbers)
• Any impediment I am facing.../ I am blocked due to...
Daily stand-up is for status update, not for any discussion. For
discussion, team members should schedule another meeting at a
different time.
ProV International
 DAILY STAND UP

Who Attends a Stand-up?

• The scrum master, the product owner, and the delivery team
should attend the stand-up daily.
• Stakeholders and Customers are encouraged to attend the
meeting and they can act as an observer, but they are not
supposed to participate in stand-ups.
• It is the scrum master's responsibility to take note of each team
member's queries and the problems they are facing.

ProV International
 SPRINT

SPRINT
A Sprint is a time boxed collection of user stories / defects to be worked
upon and accepted within the release of a product. Sprints are defined
during sprint planning meeting and completed with a sprint demo and
review meeting. A sprint is also termed as an Iteration. A sprint is done
when
• Product backup is complete.
• Performance has been tested.
• User stories have been accepted or moved to the next iteration.
• Defects have been fixed or postponed to the next iteration.

ProV International
 USER STORY

User Story
A user story is a requirement which is formulated in a few sentences in everyday
language of a user and it should be completed within an iteration.
A user story is done when:-
• All the related code have been checked-in.
• All the unit test cases have been passed.
• All the acceptance test cases have been passed.
• Help text is written.
• Product Owner has accepted the story.
Point
A Point defines how much a team can commit. A point usually refers to 8 hours. Each
story is estimated in points.
Capacity
Capacity defines how much an individual can commit. Capacity is estimated in hours.
ProV International
 PRODUCT BACKLOG

Product Backlog
Set of functional and non-functional product requirements.

Product Backlog Items

May be user stories, defects, features which are to be
developed by the agile team.

ProV International
 SPRINT PLANNING

Items in product backlog are sized and have a relative story point assigned.
Ranking has been given to portfolio items by the product owner.
Acceptance criteria has been clearly stated for each portfolio item.

Planning Process
Following are the steps involved in Sprint planning −
• Determine how many stories can fit in an iteration / sprint.
• Break these stories into tasks and assign each task to their owners.
• Each task is given estimates in hours.
• These estimates help team members to check how many task hours each
member have for the iteration.
• Team members are assigned tasks considering their velocity or capacity so that
they are not overburdened
ProV International
 SPRINT RETROSPECTION

Sprint Retrospective:- The Sprint Retrospective is an opportunity for the

Scrum Team to inspect itself and create a plan for improvements to be
enacted during the next Sprint.

The purpose of the Sprint Retrospective is to:

• Inspect how the last Sprint went with regards to people, relationships,
process, and tools;
• Identify and order the major items that went well and potential
improvements; and,
• Create a plan for implementing improvements to the way the Scrum
Team does its work.

ProV International
 AGILE - RELEASE
Release
A time box where work is done to support delivery of testable increment to a software. In
scrum, a release consists of multiple iterations.
Planning
The purpose of release planning is to create a plan to deliver an increment to the product. It
is done after every 2 to 3 months.
Planning Data
The list of data required to do release planning is as follows −
• Previous iterations or release planning results
• Feedback from various stakeholders on product, market conditions, and deadlines
• Action plans of previous releases / iterations
• Features or defects to be considered
• Velocity from previous releases/ estimates.
• Organizational and personal calendars
• Inputs from other teams and subject matter experts to manage any dependencies
ProV International
 AGILE - RELEASE
Output
The output of a release planning can be the following −
• Release plan
• Commitment
• Issues, concerns, dependencies, and assumptions which are to be
monitored
• Suggestions to improve future release planning

ProV International
 AGILE - PRIMER

ProV International
 ROLES IN AGILE
Scrum master:
A Scrum Master is a team leader and facilitator who helps the team members to follow agile
practices so that they can meet their commitments. The responsibilities of a scrum master
are as follows −
• To enable close co-operation between all roles and functions.
• To remove any blocks.
• To shield the team from any disturbances.
• To work with the organization to track the progress and processes of the company.
• To ensure that Agile Inspect & Adapt processes are leveraged properly which includes
• Daily stand-ups,
• Planned meetings,
• Demo,
• Review,
• Retrospective Meetings, and
• To facilitate team meetings and decision-making process.
ProV International
 ROLES IN AGILE

Product Owner
A Product Owner is the one who drives the product from business
perspective. The responsibilities or a Product Owner are as follows −
• To define the requirements and prioritize their values.
• To determine the release date and contents.
• To take an active role in iteration planning and release planning meetings.
• To ensure that team is working on the most valued requirement.
• To represent the voice of the customer.
• To accept the user stories that meet the definition of done and defined
acceptance criteria.

ProV International
 RESPONSIBILITIES OF A SOLN. ARCHITECT /
PRODUCT OWNER
• Convey the goal to the Delivery Team at the beginning of every Sprint and Release (one or more sprints)
• Every Sprint and Release will have fixed timeline/milestone
• Missed-out/unplanned/urgent sprint/release to be infrequent and tracked separately
• Create, prioritize and sequence the business requirement (product backlog)
• Sync with the Delivery team before committing estimation and release timelines to end customer 
• Breakdown the requirement into user stories (signed off) that are granular enough to develop quickly
• Explain the user stories to the Delivery Team
• Perform configuration validation
• Assist and approve the functional test cases
• Deliver the solution to the customer as per the agreed Release plan
• Assist to drive the Delivery Team at a sustainable pace

ProV International
 RESPONSIBILITIES OF DELIVERY TEAM
 Participate in grooming session to understand the requirement and elicit the implied
requirements, if any
 Conduct technical research, code design, prototyping and other exploration activities, if needed
 Collaborate with the Product Owner to create and fine tune user stories and acceptance tests
 Perform code development and carryout unit tests
 Maintain the code in version control tool, if applicable
 Perform acceptance tests and maintain test evidences in shared repository
 Validate the definitions of done and update JIRA to complete the Sprint
 Provide demo to the required stakeholders as applicable to receive feedback
 Deliver the solution for deployment
 Adhere to the delivery timeline agreed with Product Owner/Customer
 Inform and get the acceptance in advance from Product Owner/Customer for any potential delay
in delivery
 Continuous improvement of the team’s process…..Retrospection to Best Practices watchlist

ProV International
 BEST PRACTICES
Define the application
1 • Functions
• Target customers
• Required metrics
Create initial mockups
2 • Redesign needed for adding cosmetic values / site guidelines
• Mouseover tips, if needed
Define Information / Data flow
3 • Diagram the navigational path
• Outline all the pages in the application
Writing a Spec
4 • Separately numbered sections
• Use screenshots wherever possible
• Maintain uniform font, size, color etc.
5 Track the requirement changes, review and approve

ProV International
 SCRUM TEAM

ProV International
 BENEFITS

• Feeling of ONE TEAM

• Deliverables On Time

• Deliverables of High Quality

• Deliverables to Match the Specifications

• HAPPY CUSTOMERS (Internal & External) 

ProV International
 DELIVERABLE MILESTONES

ProV International
 ANY QUESTIONS

www.provintl.com
Thank You!

www.provintl.com