Agile software development

1. Agile Software Development

2. Topics
• Agile definition : manifesto, waterfall, principles
• Agile framework: Roles, Timeboxes, Artefacts
• Agile Roles: Team, PO, Scrum Master
• Timeboxes: planning, standups, review, retrospectives
• Artefacts: board, backlogs, story, Burndown chart
• User Stories: defining scope, DOR, DOD, estimations
• Team Management: Working Agreement, backlog
management, JIRA agile process, JIRA setup
• Benefits of Agile

3. Agile Manifesto principles
• Individuals and interactions over processes and
tools
• Working software over comprehensive
documentation
• Customer collaboration over contract
negotiation
• Responding to change over following a plan

4. Waterfall vs. Agile
• Masterpiece mentality
• Plan everything upfront
• Sequential (close phase
then move to next one)
• Build everything (even no
value features)
• Implement what was
planned
• Larger team/departments
• Alternative to waterfall
• Plan each Sprint
• Iterative approach (2
weeks sprint)
• Only build essential
features (MVP)
• Validate clients
assumptions
• Dedicated teams

5. Waterfall vs. Agile

6. Agile Framework
Roles
Scrum team
Scrum master
Product owner
Timeboxes
Planning
Stand-up
Review
Retrospective
Artefacts
Backlogs
Boards
Burndown chart

7. Agile Roles
Product owner
• Represent business
and stakeholders
• Maximize the ROI
of development
effort
• Prioritize the
Product Backlog
Scrum master
• Manage the
Scrum processes
• Keep SCRUM
artifacts visible
• Resolve
impediments
• Educate team,
organization and
client's about
agile
Scrum Team
• Scope stories
• Deliver stories of
the agreed sprint
• Technical
development and
Quality Assurance
• Collaborate with
other team
• Self-organize and
self-manage

8. Agile Timeboxes
• Sprint grooming meeting: prioritize stories for upcoming sprint
• Sprint planning meeting: prioritize the backlog
• Sprint: implement sprint backlog
• Daily stand-up: team status update to track updates and resolve any
impediments
• Sprint review meeting: demo completed stories and product owner
review
• Sprint retrospective: team evaluate sprint collaboration and make
any necessary improvements

9. Agile Artefacts
• Scrum board: physical task board with backlog stories moved
across Swimlanes
• Product backlog: ranked list of all the possible user stories/tasks to
be implemented
• Sprint backlog: prioritized list of user stories/tasks to be
implemented during the duration of a sprint
• Sprint story: details of what needs to be completed including
acceptance criteria's and estimation
• Burndown chart: chart updated daily indicating the remaining tasks
compared to the sprint total

10. Agile Board

11. User Stories
• Defines scope in an Agile Way
• Usually follows this structure: As a [type of user], I want to [goal], so
[reason]
• An example would be: "As a first time visitor of the website, I want to
register, so I can access my account".
• They are 3 critical aspects of User stories including:
1. Card: can be moves easily across the physical board Swimlanes
2. Confirmation: acceptance criteria, a way to validate the features
3. Conversation: generates discussion and remove blockers

12. Definition of Ready (DOR)
Definition of ready is an agreement on what “done” actually means.
• JIRA ticket created and properly tagged (Scrum Master)
• User story defined (Scrum Master, Product Owner)
• Acceptance criteria defined (Scrum Master, QA)
• Tasks (limited to 4 hour each) defined (Scrum Master /Team)
• Tickets t-shirt size and points size estimate completed (Scrum Master
/team)
• All UX/design assets ready (Creative)
• Impacted stakeholders are identified (Scrum Master, Product Owner)
• Known dependencies and edge cases identified (Team)

13. Definition of Done (DOD)
The Definition of done is an agreement on what “done” actually means.
Tasks
Unit test completed
Code refactoring
completed
Code/design reviewed
Story
All tasks completed
Passed acceptance
criterias
No critical bugs
Released and tested in
TEST
Moved to ready for
deployment on JIRA
board
Sprint
Completed stories demoed &
reviewed by stakeholders
JIRA board updated
Review meeting completed
Retrospective meeting
completed
Confluence sprint page
updated

14. Working Agreement
An agile team definition on how to collaborate
• JIRA ticket created and properly tagged (Scrum Master)
• User story defined (Scrum Master, Product Owner)
• Acceptance criteria defined (Scrum Master, QA)
• Tasks (limited to 4 hour each) defined (Scrum Master /Team)
• Tickets t-shirt size and points size estimate completed (Scrum Master
/team)
• All UX/design assets ready (Creative)
• Impacted stakeholders are identified (Scrum Master, Product Owner)
• Known dependencies and edge cases identified (Team)

15. Backlog management
Guidelines for managing the Agile Backlog:
• Have a Backlog grooming meeting mid sprint to prioritize stories
for upcoming sprint
• Have a Backlog planning meeting at beginning of every sprint
• Have Daily standups to manage stories for the sprint
• Have a Backlog review at the end of every sprint to demo and
resolve completed tickets and re-prioritize non-completed stories

16. JIRA agile process
Pre-Sprint:
• Prioritize stories for upcoming sprint from JIRAAgile Product Backlog
• Create User Stories from initial requirements
• Ticket size (small, medium, large) those stories
• Estimate User Stories tickets with story points during planning meeting
• Create technical sub-tasks and tag them with the relevant components
Sprint:
• Move stories on JIRAAgile board from “To do” to “In progress” when start implementing a story
and to “ready for QA” when completed
• Report on story progress daily during daily standup (and resolve any impediments)
• User Stories tickets should be tested by QA assuring it is meeting the acceptance criterias
Post-Sprint:
• Demo and review with Product Owner and key stakeholders during sprint review meeting
• Update the JIRAAgile Board and the confluence sprint page

17. JIRA setup
Guidelines for setting up an Agile JIRA board:
• Setup JIRAAgile board
• Add stories to the JIRA Product backlog (+ prioritize)
• Create necessary Swimlanes : To Do, In Progress, In QA
(ready for QA, QA in progress, ready for UAT), Done
(ready for deployment, resolved, closed)
• Add Quick Filters: Front End, Back End, Bugs, My Issues,
Recently Updated
• Create Sprint Confluence page and link completed stories

18. Benefits of Agile
• Happier customer: delivered more value for their
development money, with working software delivered
every sprints
• Happier end-users with more useful features, less
bugs and more integrated into the feedback loop
• Happier team with more autonomy and responsibility,
being self-organized and self managed
• Happier organization with improved communication
and increased productivity