Presented to TDWI Colorado Greystone Associatesdownload.101com.com/pub/tdwi/files/Agile DW for TDWI...
Transcript of Presented to TDWI Colorado Greystone Associatesdownload.101com.com/pub/tdwi/files/Agile DW for TDWI...
Presented to
TDWI Colorado
June 14, 2011
Lynn Winterboer
Greystone Associates
Lynn Winterboer Working on agile projects since 1997 and data warehousing
since 1999. Scrum Master
Project Manager
Product Owner
Business Analyst
Certified Scrum Master (CSM)
Certified Project Management Professional (PMP)
Master of International Management (MIM)
2/3 Certified Business Intelligence Professional (CBIP -Mastery Level)
Audience Survey Who is familiar with agile and scrum frameworks?
Who has worked in an agile framework?
Who has worked on an agile data warehouse project?
Agenda Definition:
What is “Agile”?
What is “Scrum”?
Discussion:
Discussion topics
Dot voting
Group discussion
Wrap-up
Preview: Your Assignment What questions do you have about how Scrum does or
doesn’t work with Data Warehousing?
Write your questions on sticky notes
One question per note
Write big so people can read it from afar
Tape the notes to the wall
Organize the questions by topic
What is Agile? Agile software development is a
group of software development methodologies
based on iterative and incremental development,
where requirements and solutions evolve through
collaboration between self-organizing, cross-functional teams.
The Agile Manifesto introduced the term in 2001.
http://en.wikipedia.org/wiki/Agile_software_development
Agile Manifesto (2001)over
Individual and Interactions Process and Tools
overWorking Software
Comprehensive Documentation
overCustomer Collaboration Contract Negotiation
overResponding to Change Following a Plan
That is, while there is value in the items on the right, we value the items on the left more.
Agile Encourages Fast Failure…
Approach Jan Feb Mar Apr May Jun
Waterfall
Agile
… with time to recover and deliver the right product at the right time
Agile Embraces Change
I think we need A, B & C
I know we need A, and think we need B & C
I know we need A & B, and C is no longer relevant
Successful organizations respond to their environments and adapt as they learn…
Some Agile Methodologies
Scrum
Extreme Programming
(XP)
Kan-ban
Lean
Feature Driven Development
(FDD)
Scrum is… One of several agile frameworks in practice today.
Simple in concept, requiring diligence in practice and dedication to a near-term goal. For example:
The product owner must be prepared to dedicate a significant amount of time to the success of the outcome.
Team members must be dedicated to the team’s efforts , not allocated across multiple projects, and willing to do anything they can to deliver on the goal.
The ScrumMaster is the facilitator of the process, not the command-and-control manager of the project. The team and product owner are the drivers on a scrum team.
Scrum is Deceptively Simple…
2-4 Weeks
24 Hours
Product
Backlog
Sprint
Backlog
Potentially Shippable Product
Increment
Daily Scrum
Ret
rosp
ecti
ve
Sp
rin
t P
lan
nin
g
Product BacklogUser
Stories
Product Backlog The product owner is responsible for the business value of
the project The product owner creates a prioritized wish list called a
product backlog, which is Dynamic—Items may be deleted or added at any time during
the project. Prioritized—Items with the highest priority are completed
first. Progressively refined—Lower priority items are intentionally
course-grained. Articulated as user stories, which are reminders to have
detailed conversations when it’s time to develop: As a <user>, I can <action> so that <result>
Sprint Planning
Sprint Planning During sprint planning, the team meets with the
product owner to pull a small chunk from the top of that wish list, a sprint backlog
The team self-organizes and decides how to implement those pieces.
A sprint backlog is A negotiated set of items from the product backlog
that a team commits to complete during the time-box of a sprint.
Items in the sprint backlog are broken into detailed tasks for the team members to complete.
Spikes Spikes are time-boxed exceptions to the standard
scrum cycle that address a particular “unknown”
A spike is usually an investigation of a user story in order to be able to estimate the work effort.
A spike can also be used to build a proof of concept, secure funding for a project, or expand knowledge about a new technology.
Spikes usually take place between sprints, though can be included in a sprint backlog.
Sprint & Daily Scrum
Sprint & Daily Scrum The team has a certain amount of time, a sprint, to
complete its work - usually two to four weeks – via self-organized, collaborative efforts.
The team meets each day to assess its progress (daily scrum) to share struggles and progress and update the sprint backlog and burn-down chart accordingly.
The burn-down chart is an at-a-glance look at the work remaining (can have two charts: one for the sprint and one for the overall release/project)
Along the way, the ScrumMaster keeps the team focused on its goal, ensuring that the team is functional and productive .
Sprint Burn-Down Chart
0
20
40
60
80
100
120
Remaining Units of WorkFast Failure – remove lower-priority requirements from the sprint to ensure the highest-priority ones get done first.
Sprint Review & Retrospective
Sprint Review & Retrospective At the end of the sprint, the team demonstrates to the
product owner what it has completed during the sprint
The work should be potentially shippable, which means that the increment/deliverable could be released to a customer or stakeholder.
The product owner makes the decision about when to actually release any functionality or deliverable.
The sprint ends with a sprint retrospective, where the team, product owner and scrum master look for ways to improve the product and the process.
Questions About Agile or Scrum?
Break 15 minutes: Visit our sponsoring vendors
Network and get to know each other
15 minutes: Break into groups of 4 - 5
What questions do you have about how scrum does or doesn’t work with data warehousing?
Write each question on a sticky note
Post the notes to the wall
Organize the questions by topic
Dot Voting Each of you has 5 stickers
Vote on the topics of most interest to you by placing your stickers on the topics posted on the wall
You may place all your stickers on one topic, or spread them out over several topics
We discuss the topics in order of the number of dots
Discussion
Resources
http://tdwi.org/http://www.scrumalliance.org/
Contact Information
Lynn Winterboer
303-859-6233
http://www.linkedin.com/in/lynnwinterboer
@agilelynn