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

Slides:



Advertisements
Similar presentations
Keith McMillan Principal, Adept Technologies Copyright (C) 2008, Adept Technologies llc.
Advertisements

Program Management School Agile & ADDIE Add-Up (AAAU) Elliott Masies Learning 2012 October 21-24, 2012.
Colin Weaver The Eleven Essential Behaviours of Successful Agile Project Teams.
Agile Software Development Robert Moore Senior Developer Curtin University.
Chapter: 3 Agile Development
Agile Software Development کاری از : مهدی هوشان استاد راهنما : استاد آدابی.
E X treme Programming & Agile Modeling Copyright © 2003 Patrick McDermott UC Berkeley Extension
A GILE SOFTWARE DEVELOPMENT : S ELF - ORGANIZING TEAM Egle Niitvägi TTU Health Care Technology.
COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. 1 Agile documentation development methodology Giby Panicker and Judith Benjamin 1-Dec-2012.
PROC-1 3. Software Process. PROC-2 What’s a process? Set of activities in creating software It involves creativity –hard to automate –Requires human judgment.
Software Development Methodologies 1. A methodology is: A collection of procedures, techniques, principles, and tools that help developers build a computer.
3 Traditional Development Methods Of (SDLC) -Prototype -Waterfall -Agile Group9 Q2 Heng shujia 0823.
Agile development By Sam Chamberlain. First a bit of history..
Project Management – An Overview Project as a metaphor – a way to approach a series of activities Contexts – construction managementt, IT development,
Agile Architecture? Paul Lund 24 th Nov Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it.
AGILE SOFTWARE DEVELOPMENT AYSE GUL YAMAN. Outline Traditional approach Agile Software Development Agile Values Agile Principles Limitations of Agile.
Agile Methods.
Software Development Models: Waterfall and Spiral Sung Hee Park Department of Mathematics and Computer Science Virginia State University August 21, 2012.
Agile Principles Suradet Jitprapaikulsarn 1. What is Agility? Effective (rapid and adaptive) response to change Effective communication among all stakeholders.
Does it work with Data Warehouses?. “We are uncovering better ways of developing software by doing it and helping others do it. Through this work we.
An Agile View of Process
Introduction to Agile.
Software engineering Process models Pavel Agejkin.
Rally: One Writer’s Perspective. Background 28 years in technical communications including Symantec, Autodesk, and Cisco. Participated in Rally-based.
1 Agile Methodology & Programming Ric Holt July 2009.
Agile Programming Principles.
The Agile Primer July 2008 © ThoughtWorks 2008.
Chapter 4 Agile Development
AGILE Methodology. AGILE  derived from the word ‘agile manifesto’, also called the Manifesto for Agile Software Development which is a formal proclamation.
OPM: the USAJOBS Product Owner Perspective By Alesia Booth & Richard Cheng.
AgileCamp Presents: Agile 101. Good luck in your presentation! This slide deck has been shared by AgileCamp Kit under the Creative Commons Attribution.
Agile Development In 2001, a group called the “Agile Alliance” signed a “manifesto” that stated: Individuals and Interactions over processes and tools.
Project Workflow. How do you do it? -Discussion-
Software Life Cycle Models. Waterfall Model  The Waterfall Model is the earliest method of structured system development.  The original waterfall model.
Extreme Programming (XP). Agile Software Development Paradigm Values individuals and interactions over processes and tools. Values working software over.
AGILE COTS Václav Pergl We are uncovering better ways of developing software by doing it and helping others do it. Through this work.
1 11/21/2015 ã 2007, Spencer Rugaber Agile Manifesto February, 2001 XP, SCRUM, DSDM, Adaptive Software Development,
CS3100 Software Project Management Agile Approaches.
Agile Methodology Paul Mohrbacher. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through.
Jeff Briggs Senior Consultant Capstone Consulting.
Agile Software Development By Kshitij Limaye CSC 532.
#AgileEd. Using Agile in the Classroom Cindy Royal, Associate Professor Texas State University slideshare.net/cindyroyal #AgileEd.
AGILE XP AND SCRUM © University of LiverpoolCOMP 319slide 1.
#2-What is Agile? Why Agile? Subtopics 1- Agile motivation for software / systems 2- Agile tenets and principles 3- Agile as a risk mitigation strategy.
- Discussion of Chapter 1 in Martin and Martin.  We are uncovering better ways of developing software by doing it and helping others do it. Through this.
10 key principles of agile software development
Module 2: What is Agile? Why use it? TLO: Given a DoD program involved in software development, the student will recognize situations where applying agile.
Extreme Programming מתודולוגיה לפיתוח פרויקטי תוכנה.
Steve Lundquist, PMP, M.Sc..  As a PMP certified program manager, there are numerous tools, processes, methodologies, and tricks that are available to.
By: Isuru Abeysekera AGILE DEVELOPMENT. WHAT IS AGILE DEVELOPMENT? Broad term used to describe several methods for a development process Introduced in.
AGILE SOFTWARE DEVELOPMENT. Agile software development : Agile software development refers to a group of software development methodologies that promotes.
Project Workflow.
Embedded Systems Software Engineering
Agile/XP Introduction
Chapter 5 Agile Development Moonzoo Kim KAIST
Agile Project Management
Agile Methodology and Scrum
AGILE SCRUM METHODOLOGY
Introduction to Agile Software Development
Principles for Agile Development
Agile Software Development
Project Workflow.
Agile Software Development Paradigms
How to Successfully Implement an Agile Project
The Agile Manifesto is based on 12 principles
Introduction to Agile Blue Ocean Workshops.
Adjective: Able to move quickly and easily. Principles and Values
Projects, Assignments, and other Assessments
SD5953 Successful Project Management AGILE SOFTWARE DEVELOPMENT
Presentation transcript:

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

Kristen McLean Founder & CEO Bookigee Hello! Who are you?

My Story (or rather the story that wasnt)

Agile

Agile is a workflow strategy

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

Key Concepts

Quick cycles

Self-organizing working 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 Idea s Produc t Data Build Learn Measur e

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 dont 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 Qs: Crowd –vs– solo creator Authorship –vs– editorship Scaleability

Kristen McLean BKGKristen Goodbye!