1 / 24

Applying Agile Methodologies to Traditional Publishing

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.

hyatt-harrington
Download Presentation

Applying Agile Methodologies to Traditional Publishing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Applying Agile Methodologiesto Traditional Publishing • Kristen McLean • Bookigee, Inc. • February 12th, 2011

  2. Kristen McLeanFounder & CEO Bookigee Who are you? Hello!

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

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

  5. User Stories Iteration Agile Push/Pull SCRUM Sprints Product Backlog Incremental Delivery Lean

  6. Agile is a workflow strategy

  7. The Agile Manifesto • We 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

  8. Key Concepts

  9. Quick cycles

  10. Self-organizing working groups

  11. Complex tasks into smaller goals

  12. Iteration

  13. Risk management

  14. Process over perfection

  15. End product from learning not knowing

  16. Test assumptions early and often

  17. The Lean Cycle Ideas Build Learn Data Product Measure

  18. Agile workflow -vs- Agile content

  19. Slow cycles • Hierarchical working groups • Final product rigid from beginning • Perfection over process • Mindset = Knower, not learners

  20. 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.

  21. Agile content?

  22. Agile content Q’s: Crowd –vs– solo creator Authorship –vs– editorship Scaleability

  23. Kristen McLeankristen@bookigee.comBKGKristen Goodbye!

More Related