Agile for Publishing - an Intro (BISG)


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Agile methodologies emerged out of the software development community starting in the 1970’s, but began to really codify in the 1990’s with the rise of several types of “lightweight” methods such as SCRUM, Extreme Programming, and Adaptive Software Development. These were all rolled up under the umbrella of Agile in 2001, when a group of developers came together to create the Manifesto for Agile Software Development which set the core principles for this type of working philosophy:
  • Simplicity—avoid complex systems, and time-intensive documentationRegular adaptation to changing circumstances—presume you don’t know the answer Accountability & empowerment— Give them what they need and trust them to get the work done.
  • Customer interaction & satisfaction extremely important—get out of the buildingClose, daily co-operation between business people and creatives—Both on the same teamSustainable 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.
  • What is Agile?
  • We MUST move beyond our typical POS-focused data toward a more collaborative, open, and qualitative data model. We must expand our ideas of DISCOVERY.
  • The most recent variation on Agile. Customer centered. Starts with the Idea, and then progresses in Build-Measure-Learn cycles.
  • Agile for Publishing - an Intro (BISG)

    1. 1. K R I S T E N M C L E A N B I S G W E B I N A R J U L Y 3 1 S T , 2 0 1 2
    3. 3. Agile
    4. 4. Agile is a workflow Agile is a philosophy Agile is a project management strategy
    5. 5. 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. -
    6. 6. Key Concepts
    7. 7. Quick cycles
    8. 8. Self-organizing working groups
    9. 9. Complex tasks into smaller goals
    10. 10. Iteration
    11. 11. Risk management
    12. 12. Transparency
    13. 13. Process over perfection
    14. 14. “Working software is the primary measure of progress”
    15. 15. End product from learning not knowing
    16. 16. Test assumptions early and often
    17. 17. THE LEAN CYCLE Ideas ProductData BuildLearn Measure Idea s Build Product Measure Data Learn customer
    18. 18. Agile workflow -vs- Agile content
    19. 19. Slow cycles Hierarchical working groups Final product rigid from beginning Perfection over process Mindset = Knower, not learners
    20. 20. A NEW MODEL Micro content Chapters & short form Excerpts & Advances •Advance copies •Sample chapters •Serial content Finished book A Book Product Owner Editor Author Production/Digital IT Sales Marketing Scrum Master/Agile manager Author Editor 10 – 12 chapter cycles Product Owner Scrum Master/Agile manager
    21. 21. THE IDEAL AGILE ENVIRONMENT? Simplicity Regular adaptation to changing circumstances Self-organizing teams Accountability, transparency & empowerment
    22. 22. Customer interaction & satisfaction important Close, daily co-operation between business and creative Sustainable development, able to maintain a constant pace Face-to-face team conversation is the best (co-location) THE IDEAL AGILE ENVIRONMENT?
    23. 23. Technical excellence and good design Completed tasks are delivered frequently (weeks rather than months) Completed tasks are the principal measure of progress THE IDEAL AGILE ENVIRONMENT?
    24. 24. New data approaches are critical
    25. 25. BACKWARD –VS- FORWARD FACING DATA moment of purchase point of sale data What? Where? When? Who? backward PAST PRESENT FUTURE consumer research Why? How? When again? What next? forward Time
    26. 26. THE LEAN CYCLE Ideas ProductData CreateLearn Measure Idea s Create Product Measure Data Learn customer The Lean Startup by Eric Ries
    27. 27. Agile workflow -vs- Agile content
    28. 28. Case Studies
    29. 29. O’REILLY MEDIA – TOOLS OF CHANGE AGILE PUBLISHING • 1st edition pubs digitally with a TOC and first few chapters • Written & reviewed in open format platform • Frequent releases building new chapters/content • Mechanism for audience engagement & feedback • Dynamic pricing model – rewards early adopters with lower prices
    30. 30. WATTPAD – WWW.WATTPAD.COM • 8 million monthly visitors • 500,000 new stories posted monthly • Recently raised $17.3m • New platform for agile brand engagement World’s largest community of readers and writers
    31. 31. HARVARD BUSINESS REVIEW–GAMIFIED TITLE RESEARCH • Comparative game behavior • Direct consumer feedback • Low cost – low risk • Could be done for jackets also •
    32. 32. BOWKER MARKET RESEARCH • Tracks 72,000 unique US books consumers annually as well as UK, AUS marke • Comprehensive research on genres, drivers, demographics, and attitudes • Custom research on behalf of publishers and associations