Download - Agile in startUps
Agile in StartUps
Who am I
-> My Name: João Cerdeira-> Team Leader-> An Agile enthusiast: Scrum / Kanban / Lean-> A true believer in OpenSource
http://twitter.com/jacerdeira [email protected]
Disclamer-> I understand your questions, but sometimes I don't have answers
-> I don't work at a Startup
-> But I usually talk with some Startup Founders
Agenda
MainPrinciples
Scrum Kanban
DevOpsContinuous
Delivery Conclusion
Agile Manifesto
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Scrum Values
Commitment
Focus
Openness
Respect
Courage
Lean Principles
Eliminate waste
Amplify learning
Decide as late as possible
Deliver as fast as possible
Empower the team
Build integrity in
See the whole
Kanban Principles
Visualize the workflow
Limit WIP
Manage Flow
Make Process Policies Explicit
Improve Collaboratively
Agenda
MainPrinciples
Scrum Kanban
DevOps ContinuousDelivery
Conclusion
Scrum
http://www.slideshare.net/rdelyon/scrum-poster
What works in Scrum
http://www.slideshare.net/rwirdemann/user-stories-for-your-product-backlog
Backlog
What works in Scrum
Retrospectives
What works in Scrum
CrossFunctional
Teams
What doesn't work in Scrum
Sprints
What doesn't work in Scrum
http://huitale.blogspot.com/2010/12/single-product-owner-model-is-broken.htmlimage: http://agilesoftwaredevelopment.com/blog/jackmilunsky/top-10-activities-product-owner
SinglePO
What doesn't work in Scrum
SingleProjectTeam
Can we remove parts of Scrum and be Agile ?
Can we remove parts of Scrum and be Agile ?
Agenda
MainPrinciples
Scrum Kanban
DevOps ContinuousDelivery
Conclusion
KanbanIntroduction
Toyota Motor Company, Taichii Ohno and Shigeo Shingo began to incorporate Ford production and other techniques
into an approach called Toyota Production System or Just In Time
http://www.strategosinc.com/just_in_time.htmhttp://totalqualitymanagement.wordpress.com/2008/10/28/lean-production-system/
The Power ofFlow
BackLog Analysis Development DoneDoing Done
US#1
The Power ofFlow
BackLog Analysis Development DoneDoing Done
US#1
The Power ofFlow
BackLog Analysis Development DoneDoing Done
US#1
The Power ofFlow
BackLog Analysis Development DoneDoing Done
US#1
The Power ofFlow
BackLog Analysis Development DoneDoing Done
US#1
The Power ofFlow
BackLog Analysis Development DoneDoing Done
US#1
The Power ofFlow
BackLog Analysis Development DoneDoing Done
US#1
The Power ofFlow
BackLog Analysis Development DoneDoing Done
US#1
The Power ofFlow
BackLog Analysis Development DoneDoing Done
US#1
The Power ofFlow
-> Shows Value Stream - like a process
-> The importance isn't to follow a process but understands why you follow it
-> Brain is a pattern matching machine - kanban board has a lot of patterns all recognizable and all provable
-> Now, people see the impact of pulling task to other team members
The Power ofFlow
-> Brain likes collaborating - The most important thing in a project is a collaborative team - People get together to achieve common objectives (the dinossaurs had eaten us if we hadn't collaborated)
-> In a kanban, the importance is about the flow and not about individual people
-> DoD in a kanban system means get the user story to the next level and don't come back
BackLog Analysis Development DoneDoing Done
US#1
US#2
US#3
US#4
US#5
WIP
BackLog Analysis Development DoneDoing Done
WIP
US#1
US#2
US#3
US#4
US#5
BackLog Analysis Development DoneDoing Done
WIP
US#1
US#2
US#3
US#4
US#5
BackLog Analysis Development DoneDoing Done
WIP
US#1
US#2
US#3
US#4
US#5
The Power ofFlow
BackLog Analysis Development DoneDoing Done
WIP
US#1
US#2
US#3
US#4
US#5
BackLog Analysis Development Done
Doing Done
(5) (2) (3)
The Power ofFlowWIP
US#1
US#2
US#3
US#4
US#5
US#1
US#2
BackLog Analysis Development Done
Doing Done
(5) (2) (3)
The Power ofFlowWIP
US#3
US#4
US#5
US#6
US#2
US#1
BackLog Analysis Development Done
Doing Done
(5) (2) (3)
The Power ofFlowWIP
US#3
US#4
US#5
US#6
US#1
BackLog Analysis Development Done
Doing Done
(5) (2) (3)
The Power ofFlowWIP
US#2
US#3
US#4
US#5
US#6
US#2
BackLog Analysis Development Done
Doing Done
(5) (2) (3)
The Power ofFlowWIP
US#1US#3
US#4
US#5
US#6
US#3
US#4
US#1
BackLog Analysis Development Done
Doing Done
(5) (2) (3)
The Power ofFlowWIP
US#2
US#5
US#6
BackLog Analysis Development Done
Doing Done
(5) (2) (3)
The Power ofFlowWIP
US#5
US#6
US#3
US#4
US#1US#2
The Power ofFlowUrgent Task
In Startups Urgent Tasks can't wait for the Sprint End
The Power ofFlowUrgent Task
In Startups Urgent Tasks can't wait for the Sprint End
Urgent Task With a Red Card
The Power ofFlowUrgent Task
In Startups Urgent Tasks can't wait for the Sprint End
Urgent Task With a Red Card
But Limit the number of Urgent TasksWIP It
Measure
BackLog Analysis Development DoneDoing Done
12 Days to complete the flow
US#1 US#1 US#1 US#1
Measure
Scrum XP way
Kanban way
LL
XLXL
MM SS
4SP5SP
3SP2SP
Tasks
-> Don't Estimate -> Just count them-> In Hours
InformationRadiator
= Task Completed
= Task
= Defect
= Priority US = High Priority US
= User Story
= Task Blocked
= Task Assignee
InformationRadiator
2011-04-30 (2011-05-30)
(Description)
L
Board AddedDate Dead Line
Priority
Size(complexity)
Who Requested the Feature
RetrospectivesPlanning
Scrum way
Sprint #1 Sprint #2 Sprint #3 Sprint #4
= Planning= Retrospective
= Demo
= Shippable Software
2 Weeks 2 Weeks 2 Weeks 2 Weeks
RetrospectivesPlanning
Kanban way
2 Weeks 2 Weeks 2 Weeks 2 Weeks
= Planning= Retrospective
= Demo
= Shippable Software
Adapt theBoard (process)
BackLog Analysis Development Acceptance
Doing Done Doing Done
Prod
Agenda
MainPrinciples
Scrum Kanban
DevOpsContinuous
Delivery Conclusion
DevOps
What matters in Software Projects ?
DevOps
What matters in Software Projects ?
DevOps
What matters in Software Projects ?
Developed features aren't completed features
DevOps
Agile is doing a great job withCross Functional Teams
DevOps
Agile is doing a great job withCross Functional Teams
DevOps
Agile is doing a great job withCross Functional Teams
But …....What about System Administrator
and Operations ?
DevOps
DevOps
ARCHITECTURE
DEVELOPMENT
QUALITY
OPERATIONS
DevOps
DEVELOPMENT
QUALITY
OPERATIONS
Agile Cross Functional TeamsA
RCHITECTURE
DevOps
http://dev2ops.org/blog/2010/2/22/what-is-devops.html
DevOps
DEVELOPMENT
QUALITY
OPERATIONS
Agile Cross Functional Teams
DevOps
ARCHITECTURE
DevOps
Business Dev Ops
Agile DevOps
DevOps
DevOps =
Agenda
MainPrinciples
Scrum Kanban
DevOps ContinuousDelivery
Conclusion
ContinuousDelivery
An usual sentence in startUps:
We can't make the client wait, we need to put this feature/bug correction As Soon As Possible in Production
ContinuousDelivery
Why companys and Teams are afraid to push code to production ?
ContinuousDelivery
Why companys and Teams are afraid to push code to production ?
Afraid that something went wrong and turn down the service causing
loss of revenue or credibility
ContinuousDelivery
Why companys and Teams are afraid to push code to production ?
Afraid that something went wrong and turn down the service causing
loss of revenue or credibility
WHY ?
ContinuousDelivery
Why companys and Teams are afraid to push code to production ?
Afraid that something went wrong and turn down the service causing
loss of revenue or credibility
WHY ?
Lack of test and Automated Builds
ContinuousDelivery
Solution:
1 –> Tests Unit TestingFunctionalIntegration
ContinuousDelivery
Solution:
1 –> Tests2 –> Automation Build Scritps
Tests
ContinuousDelivery
Solution:
1 –> Tests2 –> Automation3 –> Version Control System SubVersion
MercurialGIT
ContinuousDelivery
Solution:
1 –> Tests2 –> Automation3 –> Version Control System4 –> Continuous Integration
Builds Every CommitDedicated VCS Branch
Builds in a diferent machineTest at Every Build
ContinuousDelivery
Solution:
1 –> Tests2 –> Automation3 –> Version Control System4 –> Continuous Integration5 –> Simple Deploy Scripts
One Command DeployPuppet / Chef
ContinuousDelivery
Solution:
1 –> Tests2 –> Automation3 –> Version Control System4 –> Continuous Integration5 –> Simple Deploy Scripts6 –> Monitoring Monitoring Everything
Real Time WarningsNagios / etc
ContinuousDelivery
Solution:
1 –> Tests2 –> Automation3 –> Version Control System4 –> Continuous Integration5 –> Simple Deploy Scripts6 –> Monitoring7 –> Continuous Improvement
Examples
http://timothyfitz.wordpress.com/2009/02/10/continuous-deployment-at-imvu-doing-the-impossible-fifty-times-a-day/
http://blogs.atlassian.com/developer/2011/02/continuous_deployment_at_atlassian.html
http://www.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr
References
Agenda
MainPrinciples
Scrum Kanban
DevOpsContinuous
Delivery Conclusion
Agile Startup
MorePrescriptive
MoreAdaptative
Agile Startup
MorePrescriptive
MoreAdaptative
Big Companies StartUps
Agile Startup
RUP120+
MorePrescriptive
MoreAdaptative
Big Companies StartUps
Agile Startup
RUP XP120+ 13
MorePrescriptive
MoreAdaptative
Big Companies StartUps
Agile Startup
RUP XP Scrum120+ 13 9
MorePrescriptive
MoreAdaptative
Big Companies StartUps
Agile Startup
RUP XP Scrum Kanban120+ 13 9 3
MorePrescriptive
MoreAdaptative
Big Companies StartUps
Agile Startup
RUP XP Scrum Kanban Do Things120+ 13 9 3 0
MorePrescriptive
MoreAdaptative
Big Companies StartUps
Conclusion
Is Kanban more suitable to StartUps because has less Rules ?
Conclusion
Is Kanban more suitable to StartUps because has less Rules ?
Perhaps every company want to be as produtive as a Startup
Conclusion
Google wants to be a StartUp again
“Mr. Page said in January that he wanted to allow more projects to operate like start-ups inside of
Google, similar to how YouTube and Android currently operate.”
http://online.wsj.com/article/SB10001424052748703784004576220902706041400.html
Q&A
?