SlideShare a Scribd company logo
Agile Fundamentals
and Best Practices
Filippo Zanella
January 29th, 2015
Sellf s.r.l.
OUTLINES
1. FUNDAMENTALS
- WHY AGILE
- TEAM
- PROCESS
2. PRACTICES
- SPRINT PLANNING
- USER FEEDBACK
- TESTING
- SALES & MARKETING
3. TRELLO
INTRODUCTION
I made this slide to recap to my team at Sellf some key
concepts related to the agile (software) development.
The presented fundamentals are a summary of Scrum
directly picked from Wikipedia.
The content of the agile best practices is a (fairly faithful)
transcription of the “Agile Best Practices” screencast
presented by Jay McGraven at Codeschool.
The use-case of Trello as a tool for product management
and project tracking comes from my experience at Sellf.
FUNDAMENTALS
WHY AGILE
STAYING FOCUSED IN DELIVERING REAL
VALUE TO THE COMPANY
• No wasting time on unneeded planning docs
• No delivering features that do not fit (quite well)
customers needs
source: Jay McGraven at Codeschool
TEAM
PRODUCT OWNER
PRODUCT OWNER writes customer-centric items
(typically user stories), ranks and prioritizes them,
and adds them to the product backlog
• demonstrates the solution to key stakeholders (demo)
• announces releases
• communicates team status
• organizes milestone reviews
• educates stakeholders in the development process
• negotiates priorities, scope, funding, and schedule
• ensures that the Product Backlog is visible, transparent, and clear
source: Wikipedia
DEVELOPERS
DEVELOPMENT TEAM is responsible for delivering
potentially shippable increments of product at the end of
each Sprint (the Sprint Goal).


A Team is made up of 3–9 individuals with cross-functional
skills who do the actual work.
• analyse
• design
• develop
• test
• technical communication
• document
source: Wikipedia
SCRUM MASTER
SCRUM MASTER who is accountable for removing
impediments to the ability of the team to deliver the
product goals and deliverables
• helping the Product Owner maintain the product backlog
• determine the definition of done for the project
• coaching the team within the Scrum principles
• promote self-organization within the team
• remove all impediments to the team's progress
• facilitate team meetings to ensure regular progress
source: Wikipedia
PROCESS
SPRINT
The sprint is an effort restricted to a specific duration
The duration is fixed in advance for each sprint and is normally
between one week and one month, although two weeks is typical
Scrum emphasizes working product at the end of the Sprint that is really
“done". in the case of software, this means a system that is integrated,
fully tested, end-user documented. source: Wikipedia
MEETINGS
Each sprint is started by a planning meeting. The aim is to define a sprint backlog where the
tasks for the sprint are identified and an estimated commitment for the sprint goal is made.
Sprint planning meeting at the beginning of the sprint cycle (every 7–30 days)
• Select what work is to be done
• Prepare the Sprint Backlog that details the time it will take to do that work, with the entire team
• Eight-hour time limit for a 30-days sprint
- (First four hours) Entire team: dialogue for prioritizing the Product Backlog
- (Second four hours) Development Team: hashing out a plan for the Sprint (Backlog)
Daily scrum meeting (standup meeting):
• All members of the development team come prepared with the updates for the meeting.
• The meeting starts precisely on time even if some development team members are missing.
• The meeting should happen at the same location and time every day and it lasts 15 minutes.
During the meeting, each team member answers three questions:
1.What did I do yesterday that helped the Development Team meet the Sprint Goal?
2.What will I do today to help the Development Team meet the Sprint Goal?
3.Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?
source: Wikipedia
(USER) STORIES
In Scrum, work is expressed in the backlog as user stories. Team
members are encouraged to think of their work from the perspective of
who will use it (e.g. “text message”, “debug GPS tracking system”).
A good rule of thumb is that anything that requires more than one step to
complete or requires more than one person to complete, then it's a good
candidate to be a story.
This model of the user story is most often written like this:
As a [end user role], I want [the desire] so that [the rationale]
source: Wikipedia
PRACTICES
SPRINT PLANNING
How to make sure the team select the right stories that they can
actually deliver that sprint (that deliver value to the company)
source: Jay McGraven at Codeschool
KEY POINTS
➡LOCK REQUIREMENTS DURING SPRINTS

NOT CHANGING STORIES DURING THE SPRINT
➡TIME-BOXING

KEEP THE DURATION OF EACH ITERATION THE SAME
➡ONLY THE TEAM ESTIMATES

THE PEOPLE WHO DO THE WORK SHOULD BE THE ONE
WHO ACTUALLY ESTIMATE THE EFFORT INVOLVED
➡PRODUCT OWNER AVAILABILITY

TO ANSWER TEAM QUESTIONS
source: Jay McGraven at Codeschool
LOCK REQUIREMENTS
➡Changes in mid-sprint jeopardize work investment
‣Planning isn’t free
‣Work toward discarded/delayed features isn’t free (if you
change plans your current work is lost)
➡Increases risk
‣Other features may not get delivered
‣Other features may have defects
During a sprint iteration not changes are made
that affect the sprint call
source: Jay McGraven at Codeschool
TIME-BOXING
➡Short consistent duration
‣reduces miscommunication during the planning process
‣helps to detect problems with features sooner (i.e. extra
dialog is not needed)
‣helps to detect problems with development method
sooner (e.g. extra tests, or integration servers in place)
‣allows known end date to lend sense of focus and
urgency
‣prevents (extra) feature creep without proper oversight
All iterations should be the same duration
(usually 2-4 weeks)
source: Jay McGraven at Codeschool
TEAM ESTIMATES
➡They have unique insight on obstacles
‣Especially hard to test?
➡Estimates can reveal incorrect assumptions about
requirements
Only people actually doing the work should
estimate effort
source: Jay McGraven at Codeschool
PRODUCT OWNER
AVAILABILITY
➡has unique domain knowledge
‣worked more with the customer in the past free
‣has been a customer itself at some point
➡needed for clarification during estimation
➡at first, stories will be missing details needed to
implement
‣it has to be available for developer clarifications
➡it’s a full time job
‣if neglected, quality is gonna suffers
Know what features need to be implemented
and in what order
source: Jay McGraven at Codeschool
EXTENDING SPRINT OR
FAILING A STORY?
LET THE STORY FAIL

then just picked up and finished up and go
for the next sprint
Doing otherwise misses an opportunity to inquire into
•what went wrong
•how the process can be improved in the future
source: Jay McGraven at Codeschool
USER FEEDBACK
How to make sure it’s not getting lost in the shuffle
source: Jay McGraven at Codeschool
KEY POINTS
➡GET THEM…

without them the team is flying blind
➡…QUICKLY

one of the best reason to move away from waterfall stall
development
➡MAKE IT EASY

otherwise the users may not speak up (they’re busy after all)
source: Jay McGraven at Codeschool
DEMO EVERY SPRINT
➡Alternative is progress reports, that can be misinterpreted
➡Stakeholders need to see product early
‣They don’t have time to read detailed specs
‣Working software offers a clearer picture
‣A clearer picture allows better planning
‣Better planning means less wasted work!
source: Jay McGraven at Codeschool
MAKE FEEDBACK EASY
➡You need feedback from users too
➡But they’re busy people
‣Make ti difficult, and issues will go unreported
‣Make it easy, and their feedback will boost product quality
➡Don’t ignore what you get (read it in standup)
‣Good feedback boosts morale
‣Bad feedback is a chance to improve
source: Jay McGraven at Codeschool
TESTING
How to ensure that technical death is not creeping into
the project
source: Jay McGraven at Codeschool
KEY POINTS
➡TEST AT DEVELOPMENT TIME

adding features to a broken codebase is a recipe for disaster
➡SHARED DEFINITION OF “DONE”

can help assure that the proper tests take place
source: Jay McGraven at Codeschool
TEST AT DEV TIME
If tests are not done during development time:
➡separate test phase discovers bugs AFTER they’re easy to fix
➡incurs dangerous technical debt
‣lowered velocity
‣compounding defects
‣rising support costs
➡if testers are at capacity, developers should help
‣if testing is a pain, developers will automate more of it!
Throwing code over the wall and waiting for
defects its a bad idea
source: Jay McGraven at Codeschool
SHARED DEF OF “DONE”
When a story is “done” it means it’s in a RELEASABLE state.


A common shared definition allows to:
➡avoids miscommunication
➡keeps testing from slipping through cracks
‣automated unit test
‣automated integration test
‣manual testing
The team definition of “done” is a list of all the tasks that must
be completed before feature can be considered complete
source: Jay McGraven at Codeschool
AGILE SALES
KEY POINTS
➡SET GOALS

(e.g. budget or number of paying customers objectives)
➡SET SPRINT CYCLE 

monthly goals per person, weekly reports
➡DEFINE TOOLS

identify the instruments used by the single sales pro
➡REPORT

maintain the team updated with sales progressions
TRELLO
OUR SCENARIO
Each Trello card is a story containing different lists of specific
activities assigned to team members
HOW WE USE LISTS
Each list is a different step of the scrum process
‣ICELOG: the collector of ideas, suggestions, desiderata
that need brainstorming and approval
‣BACKLOG: features, bugs or improvements chosen
and prioritized by the product owner
‣TODO: stories that need to be completed in the current
sprint
‣DOING: stories in progress in the current sprint
‣DONE: missions accomplished :)
HOW WE USE CARDS
Each card is a story.

The order of the card determines the priority.
‣MEMBERS: all the people involved in the
completion of the story (designer, developer, …)
‣CHECKLISTS: each member has its own
checklist with the tasks that need to be completed
‣LABEL: the overall complexity / estimated time of
the specific story

More Related Content

What's hot

Behavior Driven Development Testing (BDD)
Behavior Driven Development Testing (BDD)Behavior Driven Development Testing (BDD)
Behavior Driven Development Testing (BDD)
Dignitas Digital Pvt. Ltd.
 
Agile Planning and Estimation
Agile Planning and EstimationAgile Planning and Estimation
Agile Planning and Estimation
Manish Agrawal, CSP®
 
Kanban VS Scrum
Kanban VS ScrumKanban VS Scrum
Kanban VS Scrum
Mikalai Alimenkou
 
Agile Story Writing
Agile Story WritingAgile Story Writing
Agile Story Writing
Intelliware Development Inc.
 
How to facilitate product backlog refinement sessions
How to facilitate product backlog refinement sessionsHow to facilitate product backlog refinement sessions
How to facilitate product backlog refinement sessions
LuxoftAgilePractice
 
Understanding Scrum in 30 Minutes
Understanding Scrum in 30 MinutesUnderstanding Scrum in 30 Minutes
Understanding Scrum in 30 Minutes
Altaf Najvani
 
Introduction agile scrum methodology
Introduction agile scrum methodologyIntroduction agile scrum methodology
Introduction agile scrum methodology
Amit Verma
 
What Is A Sprint Planning Meeting
What Is A Sprint Planning MeetingWhat Is A Sprint Planning Meeting
What Is A Sprint Planning Meeting
Vikrama Dhiman
 
Cucumber ppt
Cucumber pptCucumber ppt
Cucumber ppt
Qwinix Technologies
 
Elephant Carpaccio
Elephant CarpaccioElephant Carpaccio
Elephant Carpaccio
Lars Thorup
 
Agile Scrum Training Process
Agile Scrum Training ProcessAgile Scrum Training Process
Agile Scrum Training Process
Clarion Marketing
 
Workshop - Writing Good User Stories
Workshop - Writing Good User Stories Workshop - Writing Good User Stories
Workshop - Writing Good User Stories
Easy Agile
 
Agile best practices
Agile best practicesAgile best practices
Agile best practices
Areeba jabeen
 
Agile Metrics
Agile MetricsAgile Metrics
Agile Metrics
Mikalai Alimenkou
 
Agile & SCRUM basics
Agile & SCRUM basicsAgile & SCRUM basics
Agile & SCRUM basics
Arun R
 
Agile effort estimation
Agile effort estimation Agile effort estimation
Agile effort estimation
Elad Sofer
 
Scrum In 15 Minutes
Scrum In 15 MinutesScrum In 15 Minutes
Scrum In 15 Minutes
Srikanth Shreenivas
 
Sprint Planning in Scrum and How to do it without Tearing Your Eyes Out
Sprint Planning in Scrum and How to do it without Tearing Your Eyes OutSprint Planning in Scrum and How to do it without Tearing Your Eyes Out
Sprint Planning in Scrum and How to do it without Tearing Your Eyes Out
Jason Knight
 
User Story Mapping, Discover the whole story
User Story Mapping, Discover the whole storyUser Story Mapping, Discover the whole story
User Story Mapping, Discover the whole story
Jeff Patton
 
Introducing Agile User Stories
Introducing Agile User StoriesIntroducing Agile User Stories
Introducing Agile User Stories
Ram Srivastava
 

What's hot (20)

Behavior Driven Development Testing (BDD)
Behavior Driven Development Testing (BDD)Behavior Driven Development Testing (BDD)
Behavior Driven Development Testing (BDD)
 
Agile Planning and Estimation
Agile Planning and EstimationAgile Planning and Estimation
Agile Planning and Estimation
 
Kanban VS Scrum
Kanban VS ScrumKanban VS Scrum
Kanban VS Scrum
 
Agile Story Writing
Agile Story WritingAgile Story Writing
Agile Story Writing
 
How to facilitate product backlog refinement sessions
How to facilitate product backlog refinement sessionsHow to facilitate product backlog refinement sessions
How to facilitate product backlog refinement sessions
 
Understanding Scrum in 30 Minutes
Understanding Scrum in 30 MinutesUnderstanding Scrum in 30 Minutes
Understanding Scrum in 30 Minutes
 
Introduction agile scrum methodology
Introduction agile scrum methodologyIntroduction agile scrum methodology
Introduction agile scrum methodology
 
What Is A Sprint Planning Meeting
What Is A Sprint Planning MeetingWhat Is A Sprint Planning Meeting
What Is A Sprint Planning Meeting
 
Cucumber ppt
Cucumber pptCucumber ppt
Cucumber ppt
 
Elephant Carpaccio
Elephant CarpaccioElephant Carpaccio
Elephant Carpaccio
 
Agile Scrum Training Process
Agile Scrum Training ProcessAgile Scrum Training Process
Agile Scrum Training Process
 
Workshop - Writing Good User Stories
Workshop - Writing Good User Stories Workshop - Writing Good User Stories
Workshop - Writing Good User Stories
 
Agile best practices
Agile best practicesAgile best practices
Agile best practices
 
Agile Metrics
Agile MetricsAgile Metrics
Agile Metrics
 
Agile & SCRUM basics
Agile & SCRUM basicsAgile & SCRUM basics
Agile & SCRUM basics
 
Agile effort estimation
Agile effort estimation Agile effort estimation
Agile effort estimation
 
Scrum In 15 Minutes
Scrum In 15 MinutesScrum In 15 Minutes
Scrum In 15 Minutes
 
Sprint Planning in Scrum and How to do it without Tearing Your Eyes Out
Sprint Planning in Scrum and How to do it without Tearing Your Eyes OutSprint Planning in Scrum and How to do it without Tearing Your Eyes Out
Sprint Planning in Scrum and How to do it without Tearing Your Eyes Out
 
User Story Mapping, Discover the whole story
User Story Mapping, Discover the whole storyUser Story Mapping, Discover the whole story
User Story Mapping, Discover the whole story
 
Introducing Agile User Stories
Introducing Agile User StoriesIntroducing Agile User Stories
Introducing Agile User Stories
 

Similar to Agile Fundamentals and Best Practices (with Trello)

CampusSDN2017 - Jawdat: Product Management and Agile Development
CampusSDN2017 - Jawdat: Product Management and Agile DevelopmentCampusSDN2017 - Jawdat: Product Management and Agile Development
CampusSDN2017 - Jawdat: Product Management and Agile Development
JawdatTI
 
Agile Methodology and Tools
Agile Methodology and ToolsAgile Methodology and Tools
Agile Methodology and Tools
Naresh Gajuveni
 
Presentation on agile methodology
Presentation on agile methodologyPresentation on agile methodology
Presentation on agile methodology
Ashish Jain, CSM, Prince2 Practitioner
 
Introduction to Agile & scrum
Introduction to Agile & scrumIntroduction to Agile & scrum
Introduction to Agile & scrum
Elad Sofer
 
Scrum referencecard
Scrum referencecardScrum referencecard
Scrum referencecard
Suresh Kumar
 
Scrum Framework Explained
Scrum Framework ExplainedScrum Framework Explained
Scrum Framework Explained
Nacho Montoya
 
Agile methodology
Agile methodologyAgile methodology
Agile methodology
subash kumar
 
Agile (Scrum)
Agile (Scrum)Agile (Scrum)
Agile (Scrum)
Dom Cushnan
 
Agile practices for management
Agile practices for managementAgile practices for management
Agile practices for management
Icalia Labs
 
A Pattern-Language-for-software-Development
A Pattern-Language-for-software-DevelopmentA Pattern-Language-for-software-Development
A Pattern-Language-for-software-Development
Shiraz316
 
BAAgileQA
BAAgileQABAAgileQA
Let’s Play Agile ! 12-09-15-testers_hub
Let’s  Play  Agile ! 12-09-15-testers_hubLet’s  Play  Agile ! 12-09-15-testers_hub
Let’s Play Agile ! 12-09-15-testers_hub
Owner Tester's Hub
 
Agile Modeling & Scrum Development.pptx
Agile Modeling & Scrum Development.pptxAgile Modeling & Scrum Development.pptx
Agile Modeling & Scrum Development.pptx
Samira AlShahrani
 
Agile_basics
Agile_basicsAgile_basics
Agile_basics
Mithilesh Singh
 
Agile, not just for software
Agile, not just for softwareAgile, not just for software
Agile, not just for software
John Paz
 
Agile software-development-overview-1231560734008086-2
Agile software-development-overview-1231560734008086-2Agile software-development-overview-1231560734008086-2
Agile software-development-overview-1231560734008086-2
shankar chinn
 
Scrum-Agile : An Introduction
Scrum-Agile : An IntroductionScrum-Agile : An Introduction
Scrum-Agile : An Introduction
Global SQA
 
Ssw forte-agile-seminar
Ssw forte-agile-seminarSsw forte-agile-seminar
Ssw forte-agile-seminar
SSW
 
Agile Development: What is a Sprint Cycle?
Agile Development: What is a Sprint Cycle?Agile Development: What is a Sprint Cycle?
Agile Development: What is a Sprint Cycle?
Flowace.ai
 
Agile software development compfest 13
Agile software development compfest 13Agile software development compfest 13
Agile software development compfest 13
Panji Gautama
 

Similar to Agile Fundamentals and Best Practices (with Trello) (20)

CampusSDN2017 - Jawdat: Product Management and Agile Development
CampusSDN2017 - Jawdat: Product Management and Agile DevelopmentCampusSDN2017 - Jawdat: Product Management and Agile Development
CampusSDN2017 - Jawdat: Product Management and Agile Development
 
Agile Methodology and Tools
Agile Methodology and ToolsAgile Methodology and Tools
Agile Methodology and Tools
 
Presentation on agile methodology
Presentation on agile methodologyPresentation on agile methodology
Presentation on agile methodology
 
Introduction to Agile & scrum
Introduction to Agile & scrumIntroduction to Agile & scrum
Introduction to Agile & scrum
 
Scrum referencecard
Scrum referencecardScrum referencecard
Scrum referencecard
 
Scrum Framework Explained
Scrum Framework ExplainedScrum Framework Explained
Scrum Framework Explained
 
Agile methodology
Agile methodologyAgile methodology
Agile methodology
 
Agile (Scrum)
Agile (Scrum)Agile (Scrum)
Agile (Scrum)
 
Agile practices for management
Agile practices for managementAgile practices for management
Agile practices for management
 
A Pattern-Language-for-software-Development
A Pattern-Language-for-software-DevelopmentA Pattern-Language-for-software-Development
A Pattern-Language-for-software-Development
 
BAAgileQA
BAAgileQABAAgileQA
BAAgileQA
 
Let’s Play Agile ! 12-09-15-testers_hub
Let’s  Play  Agile ! 12-09-15-testers_hubLet’s  Play  Agile ! 12-09-15-testers_hub
Let’s Play Agile ! 12-09-15-testers_hub
 
Agile Modeling & Scrum Development.pptx
Agile Modeling & Scrum Development.pptxAgile Modeling & Scrum Development.pptx
Agile Modeling & Scrum Development.pptx
 
Agile_basics
Agile_basicsAgile_basics
Agile_basics
 
Agile, not just for software
Agile, not just for softwareAgile, not just for software
Agile, not just for software
 
Agile software-development-overview-1231560734008086-2
Agile software-development-overview-1231560734008086-2Agile software-development-overview-1231560734008086-2
Agile software-development-overview-1231560734008086-2
 
Scrum-Agile : An Introduction
Scrum-Agile : An IntroductionScrum-Agile : An Introduction
Scrum-Agile : An Introduction
 
Ssw forte-agile-seminar
Ssw forte-agile-seminarSsw forte-agile-seminar
Ssw forte-agile-seminar
 
Agile Development: What is a Sprint Cycle?
Agile Development: What is a Sprint Cycle?Agile Development: What is a Sprint Cycle?
Agile Development: What is a Sprint Cycle?
 
Agile software development compfest 13
Agile software development compfest 13Agile software development compfest 13
Agile software development compfest 13
 

Recently uploaded

m249-saw PMI To familiarize the soldier with the M249 Squad Automatic Weapon ...
m249-saw PMI To familiarize the soldier with the M249 Squad Automatic Weapon ...m249-saw PMI To familiarize the soldier with the M249 Squad Automatic Weapon ...
m249-saw PMI To familiarize the soldier with the M249 Squad Automatic Weapon ...
LinghuaKong2
 
一比一原版(philau毕业证书)美国费城大学毕业证如何办理
一比一原版(philau毕业证书)美国费城大学毕业证如何办理一比一原版(philau毕业证书)美国费城大学毕业证如何办理
一比一原版(philau毕业证书)美国费城大学毕业证如何办理
nozaxy
 
team presentation of the role and responsibility of HSE teamreviewed.pptx
team presentation of the role and responsibility of HSE teamreviewed.pptxteam presentation of the role and responsibility of HSE teamreviewed.pptx
team presentation of the role and responsibility of HSE teamreviewed.pptx
ProsperOghalomeno1
 
9 Ways Managers Kill Morale (and What to Do Instead)
9 Ways Managers Kill Morale (and What to Do Instead)9 Ways Managers Kill Morale (and What to Do Instead)
9 Ways Managers Kill Morale (and What to Do Instead)
experienceprosarah
 
Designing and Sustaining Large-Scale Value-Centered Agile Ecosystems (powered...
Designing and Sustaining Large-Scale Value-Centered Agile Ecosystems (powered...Designing and Sustaining Large-Scale Value-Centered Agile Ecosystems (powered...
Designing and Sustaining Large-Scale Value-Centered Agile Ecosystems (powered...
Alexey Krivitsky
 
Maximize Your Efficiency with This Comprehensive Project Management Platform ...
Maximize Your Efficiency with This Comprehensive Project Management Platform ...Maximize Your Efficiency with This Comprehensive Project Management Platform ...
Maximize Your Efficiency with This Comprehensive Project Management Platform ...
SOFTTECHHUB
 
A comprehensive-study-of-biparjoy-cyclone-disaster-management-in-gujarat-a-ca...
A comprehensive-study-of-biparjoy-cyclone-disaster-management-in-gujarat-a-ca...A comprehensive-study-of-biparjoy-cyclone-disaster-management-in-gujarat-a-ca...
A comprehensive-study-of-biparjoy-cyclone-disaster-management-in-gujarat-a-ca...
Samirsinh Parmar
 
From Concept to reality : Implementing Lean Managements DMAIC Methodology for...
From Concept to reality : Implementing Lean Managements DMAIC Methodology for...From Concept to reality : Implementing Lean Managements DMAIC Methodology for...
From Concept to reality : Implementing Lean Managements DMAIC Methodology for...
Rokibul Hasan
 
Customer Relationship Managemenet’s Impact on Customer Satisfaction and Perfo...
Customer Relationship Managemenet’s Impact on Customer Satisfaction and Perfo...Customer Relationship Managemenet’s Impact on Customer Satisfaction and Perfo...
Customer Relationship Managemenet’s Impact on Customer Satisfaction and Perfo...
Istanbul Beykent University (İstanbul Beykent Üniversitesi)
 
Neal Elbaum Shares Top 5 Trends Shaping the Logistics Industry in 2024
Neal Elbaum Shares Top 5 Trends Shaping the Logistics Industry in 2024Neal Elbaum Shares Top 5 Trends Shaping the Logistics Industry in 2024
Neal Elbaum Shares Top 5 Trends Shaping the Logistics Industry in 2024
Neal Elbaum
 
Small Business Management An Entrepreneur’s Guidebook 8th edition by Byrd tes...
Small Business Management An Entrepreneur’s Guidebook 8th edition by Byrd tes...Small Business Management An Entrepreneur’s Guidebook 8th edition by Byrd tes...
Small Business Management An Entrepreneur’s Guidebook 8th edition by Byrd tes...
ssuserf63bd7
 

Recently uploaded (11)

m249-saw PMI To familiarize the soldier with the M249 Squad Automatic Weapon ...
m249-saw PMI To familiarize the soldier with the M249 Squad Automatic Weapon ...m249-saw PMI To familiarize the soldier with the M249 Squad Automatic Weapon ...
m249-saw PMI To familiarize the soldier with the M249 Squad Automatic Weapon ...
 
一比一原版(philau毕业证书)美国费城大学毕业证如何办理
一比一原版(philau毕业证书)美国费城大学毕业证如何办理一比一原版(philau毕业证书)美国费城大学毕业证如何办理
一比一原版(philau毕业证书)美国费城大学毕业证如何办理
 
team presentation of the role and responsibility of HSE teamreviewed.pptx
team presentation of the role and responsibility of HSE teamreviewed.pptxteam presentation of the role and responsibility of HSE teamreviewed.pptx
team presentation of the role and responsibility of HSE teamreviewed.pptx
 
9 Ways Managers Kill Morale (and What to Do Instead)
9 Ways Managers Kill Morale (and What to Do Instead)9 Ways Managers Kill Morale (and What to Do Instead)
9 Ways Managers Kill Morale (and What to Do Instead)
 
Designing and Sustaining Large-Scale Value-Centered Agile Ecosystems (powered...
Designing and Sustaining Large-Scale Value-Centered Agile Ecosystems (powered...Designing and Sustaining Large-Scale Value-Centered Agile Ecosystems (powered...
Designing and Sustaining Large-Scale Value-Centered Agile Ecosystems (powered...
 
Maximize Your Efficiency with This Comprehensive Project Management Platform ...
Maximize Your Efficiency with This Comprehensive Project Management Platform ...Maximize Your Efficiency with This Comprehensive Project Management Platform ...
Maximize Your Efficiency with This Comprehensive Project Management Platform ...
 
A comprehensive-study-of-biparjoy-cyclone-disaster-management-in-gujarat-a-ca...
A comprehensive-study-of-biparjoy-cyclone-disaster-management-in-gujarat-a-ca...A comprehensive-study-of-biparjoy-cyclone-disaster-management-in-gujarat-a-ca...
A comprehensive-study-of-biparjoy-cyclone-disaster-management-in-gujarat-a-ca...
 
From Concept to reality : Implementing Lean Managements DMAIC Methodology for...
From Concept to reality : Implementing Lean Managements DMAIC Methodology for...From Concept to reality : Implementing Lean Managements DMAIC Methodology for...
From Concept to reality : Implementing Lean Managements DMAIC Methodology for...
 
Customer Relationship Managemenet’s Impact on Customer Satisfaction and Perfo...
Customer Relationship Managemenet’s Impact on Customer Satisfaction and Perfo...Customer Relationship Managemenet’s Impact on Customer Satisfaction and Perfo...
Customer Relationship Managemenet’s Impact on Customer Satisfaction and Perfo...
 
Neal Elbaum Shares Top 5 Trends Shaping the Logistics Industry in 2024
Neal Elbaum Shares Top 5 Trends Shaping the Logistics Industry in 2024Neal Elbaum Shares Top 5 Trends Shaping the Logistics Industry in 2024
Neal Elbaum Shares Top 5 Trends Shaping the Logistics Industry in 2024
 
Small Business Management An Entrepreneur’s Guidebook 8th edition by Byrd tes...
Small Business Management An Entrepreneur’s Guidebook 8th edition by Byrd tes...Small Business Management An Entrepreneur’s Guidebook 8th edition by Byrd tes...
Small Business Management An Entrepreneur’s Guidebook 8th edition by Byrd tes...
 

Agile Fundamentals and Best Practices (with Trello)

  • 1. Agile Fundamentals and Best Practices Filippo Zanella January 29th, 2015 Sellf s.r.l.
  • 2. OUTLINES 1. FUNDAMENTALS - WHY AGILE - TEAM - PROCESS 2. PRACTICES - SPRINT PLANNING - USER FEEDBACK - TESTING - SALES & MARKETING 3. TRELLO
  • 3. INTRODUCTION I made this slide to recap to my team at Sellf some key concepts related to the agile (software) development. The presented fundamentals are a summary of Scrum directly picked from Wikipedia. The content of the agile best practices is a (fairly faithful) transcription of the “Agile Best Practices” screencast presented by Jay McGraven at Codeschool. The use-case of Trello as a tool for product management and project tracking comes from my experience at Sellf.
  • 5. WHY AGILE STAYING FOCUSED IN DELIVERING REAL VALUE TO THE COMPANY • No wasting time on unneeded planning docs • No delivering features that do not fit (quite well) customers needs source: Jay McGraven at Codeschool
  • 7. PRODUCT OWNER PRODUCT OWNER writes customer-centric items (typically user stories), ranks and prioritizes them, and adds them to the product backlog • demonstrates the solution to key stakeholders (demo) • announces releases • communicates team status • organizes milestone reviews • educates stakeholders in the development process • negotiates priorities, scope, funding, and schedule • ensures that the Product Backlog is visible, transparent, and clear source: Wikipedia
  • 8. DEVELOPERS DEVELOPMENT TEAM is responsible for delivering potentially shippable increments of product at the end of each Sprint (the Sprint Goal). 
 A Team is made up of 3–9 individuals with cross-functional skills who do the actual work. • analyse • design • develop • test • technical communication • document source: Wikipedia
  • 9. SCRUM MASTER SCRUM MASTER who is accountable for removing impediments to the ability of the team to deliver the product goals and deliverables • helping the Product Owner maintain the product backlog • determine the definition of done for the project • coaching the team within the Scrum principles • promote self-organization within the team • remove all impediments to the team's progress • facilitate team meetings to ensure regular progress source: Wikipedia
  • 11. SPRINT The sprint is an effort restricted to a specific duration The duration is fixed in advance for each sprint and is normally between one week and one month, although two weeks is typical Scrum emphasizes working product at the end of the Sprint that is really “done". in the case of software, this means a system that is integrated, fully tested, end-user documented. source: Wikipedia
  • 12. MEETINGS Each sprint is started by a planning meeting. The aim is to define a sprint backlog where the tasks for the sprint are identified and an estimated commitment for the sprint goal is made. Sprint planning meeting at the beginning of the sprint cycle (every 7–30 days) • Select what work is to be done • Prepare the Sprint Backlog that details the time it will take to do that work, with the entire team • Eight-hour time limit for a 30-days sprint - (First four hours) Entire team: dialogue for prioritizing the Product Backlog - (Second four hours) Development Team: hashing out a plan for the Sprint (Backlog) Daily scrum meeting (standup meeting): • All members of the development team come prepared with the updates for the meeting. • The meeting starts precisely on time even if some development team members are missing. • The meeting should happen at the same location and time every day and it lasts 15 minutes. During the meeting, each team member answers three questions: 1.What did I do yesterday that helped the Development Team meet the Sprint Goal? 2.What will I do today to help the Development Team meet the Sprint Goal? 3.Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal? source: Wikipedia
  • 13. (USER) STORIES In Scrum, work is expressed in the backlog as user stories. Team members are encouraged to think of their work from the perspective of who will use it (e.g. “text message”, “debug GPS tracking system”). A good rule of thumb is that anything that requires more than one step to complete or requires more than one person to complete, then it's a good candidate to be a story. This model of the user story is most often written like this: As a [end user role], I want [the desire] so that [the rationale] source: Wikipedia
  • 15. SPRINT PLANNING How to make sure the team select the right stories that they can actually deliver that sprint (that deliver value to the company) source: Jay McGraven at Codeschool
  • 16. KEY POINTS ➡LOCK REQUIREMENTS DURING SPRINTS
 NOT CHANGING STORIES DURING THE SPRINT ➡TIME-BOXING
 KEEP THE DURATION OF EACH ITERATION THE SAME ➡ONLY THE TEAM ESTIMATES
 THE PEOPLE WHO DO THE WORK SHOULD BE THE ONE WHO ACTUALLY ESTIMATE THE EFFORT INVOLVED ➡PRODUCT OWNER AVAILABILITY
 TO ANSWER TEAM QUESTIONS source: Jay McGraven at Codeschool
  • 17. LOCK REQUIREMENTS ➡Changes in mid-sprint jeopardize work investment ‣Planning isn’t free ‣Work toward discarded/delayed features isn’t free (if you change plans your current work is lost) ➡Increases risk ‣Other features may not get delivered ‣Other features may have defects During a sprint iteration not changes are made that affect the sprint call source: Jay McGraven at Codeschool
  • 18. TIME-BOXING ➡Short consistent duration ‣reduces miscommunication during the planning process ‣helps to detect problems with features sooner (i.e. extra dialog is not needed) ‣helps to detect problems with development method sooner (e.g. extra tests, or integration servers in place) ‣allows known end date to lend sense of focus and urgency ‣prevents (extra) feature creep without proper oversight All iterations should be the same duration (usually 2-4 weeks) source: Jay McGraven at Codeschool
  • 19. TEAM ESTIMATES ➡They have unique insight on obstacles ‣Especially hard to test? ➡Estimates can reveal incorrect assumptions about requirements Only people actually doing the work should estimate effort source: Jay McGraven at Codeschool
  • 20. PRODUCT OWNER AVAILABILITY ➡has unique domain knowledge ‣worked more with the customer in the past free ‣has been a customer itself at some point ➡needed for clarification during estimation ➡at first, stories will be missing details needed to implement ‣it has to be available for developer clarifications ➡it’s a full time job ‣if neglected, quality is gonna suffers Know what features need to be implemented and in what order source: Jay McGraven at Codeschool
  • 21. EXTENDING SPRINT OR FAILING A STORY? LET THE STORY FAIL
 then just picked up and finished up and go for the next sprint Doing otherwise misses an opportunity to inquire into •what went wrong •how the process can be improved in the future source: Jay McGraven at Codeschool
  • 22. USER FEEDBACK How to make sure it’s not getting lost in the shuffle source: Jay McGraven at Codeschool
  • 23. KEY POINTS ➡GET THEM…
 without them the team is flying blind ➡…QUICKLY
 one of the best reason to move away from waterfall stall development ➡MAKE IT EASY
 otherwise the users may not speak up (they’re busy after all) source: Jay McGraven at Codeschool
  • 24. DEMO EVERY SPRINT ➡Alternative is progress reports, that can be misinterpreted ➡Stakeholders need to see product early ‣They don’t have time to read detailed specs ‣Working software offers a clearer picture ‣A clearer picture allows better planning ‣Better planning means less wasted work! source: Jay McGraven at Codeschool
  • 25. MAKE FEEDBACK EASY ➡You need feedback from users too ➡But they’re busy people ‣Make ti difficult, and issues will go unreported ‣Make it easy, and their feedback will boost product quality ➡Don’t ignore what you get (read it in standup) ‣Good feedback boosts morale ‣Bad feedback is a chance to improve source: Jay McGraven at Codeschool
  • 26. TESTING How to ensure that technical death is not creeping into the project source: Jay McGraven at Codeschool
  • 27. KEY POINTS ➡TEST AT DEVELOPMENT TIME
 adding features to a broken codebase is a recipe for disaster ➡SHARED DEFINITION OF “DONE”
 can help assure that the proper tests take place source: Jay McGraven at Codeschool
  • 28. TEST AT DEV TIME If tests are not done during development time: ➡separate test phase discovers bugs AFTER they’re easy to fix ➡incurs dangerous technical debt ‣lowered velocity ‣compounding defects ‣rising support costs ➡if testers are at capacity, developers should help ‣if testing is a pain, developers will automate more of it! Throwing code over the wall and waiting for defects its a bad idea source: Jay McGraven at Codeschool
  • 29. SHARED DEF OF “DONE” When a story is “done” it means it’s in a RELEASABLE state. 
 A common shared definition allows to: ➡avoids miscommunication ➡keeps testing from slipping through cracks ‣automated unit test ‣automated integration test ‣manual testing The team definition of “done” is a list of all the tasks that must be completed before feature can be considered complete source: Jay McGraven at Codeschool
  • 31. KEY POINTS ➡SET GOALS
 (e.g. budget or number of paying customers objectives) ➡SET SPRINT CYCLE 
 monthly goals per person, weekly reports ➡DEFINE TOOLS
 identify the instruments used by the single sales pro ➡REPORT
 maintain the team updated with sales progressions
  • 33. OUR SCENARIO Each Trello card is a story containing different lists of specific activities assigned to team members
  • 34. HOW WE USE LISTS Each list is a different step of the scrum process ‣ICELOG: the collector of ideas, suggestions, desiderata that need brainstorming and approval ‣BACKLOG: features, bugs or improvements chosen and prioritized by the product owner ‣TODO: stories that need to be completed in the current sprint ‣DOING: stories in progress in the current sprint ‣DONE: missions accomplished :)
  • 35. HOW WE USE CARDS Each card is a story.
 The order of the card determines the priority. ‣MEMBERS: all the people involved in the completion of the story (designer, developer, …) ‣CHECKLISTS: each member has its own checklist with the tasks that need to be completed ‣LABEL: the overall complexity / estimated time of the specific story