Applying Agile Methodologies to Traditional Publishing Kristen McLean Bookigee, Inc. February 12 th,...
-
Upload
isabella-ruiz -
Category
Documents
-
view
213 -
download
0
Transcript of Applying Agile Methodologies to Traditional Publishing Kristen McLean Bookigee, Inc. February 12 th,...
Applying Agile Methodologies
to Traditional Publishing
Kristen McLeanBookigee, Inc.
February 12th, 2011
Kristen McLeanFounder & CEO
Bookigee
Hello!Who are you?
My Story (or rather the story that wasn’t)
My Story (or rather the story that wasn’t)
Agile
Agile is a workflow strategy
The Agile ManifestoWe are uncovering better ways of developing software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and
tools
Working software over comprehensive
documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
-www.agilemanifesto.org
Key Concepts
Quick cycles
Self-organizingworking groups
Complex tasks into smaller goals
Iteration
Risk management
Process over perfection
End product from learning not
knowing
Test assumptions early and often
The Lean Cycle Ideas
Product
Data
BuildLearn
Measure
Agile workflow -vs-
Agile content
Slow cycles
Hierarchical working groups
Final product rigid from beginning
Perfection over process
Mindset = Knower, not learners
What would an Agile environment look like?
Simplicity—avoid complex systems, and time-intensive documentation
Regular adaptation to changing circumstances—presume you don’t know the answer
Self-organizing teams with flexible skills—get highly talented and interdisciplinary individuals
Accountability & empowerment— Give them what they need and trust them to get the work done.
Customer interaction & satisfaction extremely important—get out of the building
Close, daily co-operation between business people and creatives—Both on the same team
Sustainable development, able to maintain a constant pace—each person should be able to commit only to what they can do in a day, a week, or a production cycle. Cut back features in order to deliver on time.
Face-to-face conversation is the best form of communication (co-location)—put the entire team in one place.
Continuous attention to technical excellence and good design—Produce less, but make it better.
Completed tasks are delivered frequently (weeks rather than months)
Completed tasks are the principal measure of progress—focus on real stuff, not on rituals, documentation, or other internal benchmarks that do nothing for your customer.
Agile content?
Agile content Q’s:
Crowd –vs– solo creator
Authorship –vs– editorship
Scaleability