applying agile methodologies to traditional publishing

24
Applying Agile Methodologies to Traditional Publishing Kristen McLean Bookigee, Inc. February 12 th , 2011

Upload: hyatt-harrington

Post on 02-Jan-2016

28 views

Category:

Documents


0 download

DESCRIPTION

Applying Agile Methodologies to Traditional Publishing. Kristen McLean Bookigee , Inc. February 12 th , 2011. Kristen McLean Founder & CEO Bookigee. Who are you?. Hello!. My Story (or rather the story that wasn ’ t). My Story (or rather the story that wasn ’ t). User Stories. Iteration. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Applying Agile Methodologies to Traditional Publishing

Applying Agile Methodologies

to Traditional Publishing

Kristen McLeanBookigee, Inc.

February 12th, 2011

Page 2: Applying Agile Methodologies to Traditional Publishing

Kristen McLeanFounder & CEO

Bookigee

Hello!Who are you?

Page 3: Applying Agile Methodologies to Traditional Publishing

My Story (or rather the story that wasn’t)

Page 4: Applying Agile Methodologies to Traditional Publishing

My Story (or rather the story that wasn’t)

Page 5: Applying Agile Methodologies to Traditional Publishing

Agile

Page 6: Applying Agile Methodologies to Traditional Publishing
Page 7: Applying Agile Methodologies to Traditional Publishing

Agile is a workflow strategy

Page 8: Applying Agile Methodologies to Traditional Publishing

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

Page 9: Applying Agile Methodologies to Traditional Publishing

Key Concepts

Page 10: Applying Agile Methodologies to Traditional Publishing

Quick cycles

Page 11: Applying Agile Methodologies to Traditional Publishing

Self-organizingworking groups

Page 12: Applying Agile Methodologies to Traditional Publishing

Complex tasks into smaller goals

Page 13: Applying Agile Methodologies to Traditional Publishing

Iteration

Page 14: Applying Agile Methodologies to Traditional Publishing

Risk management

Page 15: Applying Agile Methodologies to Traditional Publishing

Process over perfection

Page 16: Applying Agile Methodologies to Traditional Publishing

End product from learning not

knowing

Page 17: Applying Agile Methodologies to Traditional Publishing

Test assumptions early and often

Page 18: Applying Agile Methodologies to Traditional Publishing

The Lean Cycle Ideas

Product

Data

BuildLearn

Measure

Page 19: Applying Agile Methodologies to Traditional Publishing

Agile workflow -vs-

Agile content

Page 20: Applying Agile Methodologies to Traditional Publishing

Slow cycles

Hierarchical working groups

Final product rigid from beginning

Perfection over process

Mindset = Knower, not learners

Page 21: Applying Agile Methodologies to Traditional Publishing

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.

Page 22: Applying Agile Methodologies to Traditional Publishing

Agile content?

Page 23: Applying Agile Methodologies to Traditional Publishing

Agile content Q’s:

Crowd –vs– solo creator

Authorship –vs– editorship

Scaleability

Page 24: Applying Agile Methodologies to Traditional Publishing

Kristen [email protected]

BKGKristen

Goodbye!