What methodology does Green Hill use for book production?
I won’t go into the details of our project methodology because it’s like KFC’s ‘secret herbs and spices’. It’s how we’ve become an industry leader delivering a real competitive advantage for our company and how we provide great, cost-effective, quality results for authors. It’s a project management ‘architecture’ developed over many years and the details of that remain with us! One author asked ‘Can you explain every step of your process?’ We undertake 124 different actions/tasks to publish a book and don’t unpack our processes in detail for authors. It would take many hours.
Green Hill uses Waterfall methodology for book production
Having said that, all authors do need to know that we use a Waterfall approach. When an author joins Green Hill they join a project that is contracted to perform a Waterfall methodology.

Waterfall method – each phase starts after the completion of the prior
When we start a project the author receives the Author Guide which outlines how we communicate (in-person and online), what we do, what the author needs to do, when we complete phases and in which order each component is undertaken. Importantly it is a linear process – step by step with the next step starting after the completion of the one prior.
Waterfall projects can be completed in just 6-8 weeks after receipt of a final manuscript.
This project methodology is a formula for book publishing success!
What if an author needs an Agile approach?

Agile method – great if the author has plenty of time and deep pockets
If an author wants to adopt an Agile approach to their project we can certainly do that. However an Agile approach might cost 2-3 times as much as a Waterfall project. A Green Hill Publishing contract and the associated fixed price is for a Waterfall project methodology as clearly outlined in our Terms of Service. Switching or starting with an Agile methodology must be negotiated, with cost and time being major points for mutual clarification and agreement.
Agile and Scrums are often a formula for a lengthy and costly book production process.
Authors might say, ‘I’ll know the best book design when I see it’. They might provide several versions of their manuscript. They might need to see 10 cover designs. Sometimes this is called ‘experimental design’ and can seemingly never end, and when it does end the book design isn’t very good. Often a designer’s original clear and powerful book concept has been tampered with, reshaped, amended, modified and massaged into something mediocre.
Sometimes with the Agile process, far too many people are involved. Authors might want to involve spouses, friends or colleagues in decision making and providing feedback. One author conducted an online survey asking people to vote on the best elements of several cover designs and then instructed the designer to mash the most popular elements together – it was a truly horrible book cover – a Frankenstein.
Under Agile, authors might want to remove chapters when the book has reached advanced design. One author wanted to handle paper samples for print and see embossing, way before he had finished writing the manuscript, let alone before design was underway. Another’s project, after an initial deadline of 2 months, stretched over 2 and a half years from start to completion.
It’s all expensive and time consuming.
Agile – it’s for the big spenders and might be for you if you believe your thoughts are not yet well organised and you have the financial means. And you have plenty of time to invest.
Waterfall and Agile book production project management methodologies compared

Agile is expensive and slow, Waterfall is rapid and cost effective.
The two methodologies differ in execution, effect and results. Here I’ll visually show a couple of the major differences that will affect every self-published author.
The two most important concerns routinely become cost and time. Understandably most authors come to us with cost and time constraints. Very few have unlimited budgets. And for most authors, after lengthy periods in which they have crafted their content, finally the book’s ‘time has come’. If it’s not urgent, it’s timely to get their content published.
This can be easily explained in the overlay of the matrix/ Venn Diagram shown here. In essence, Waterfall is cost effective and rapid, whereas Agile is expensive and slow.
Are you ready for Waterfall or is Agile best suited?
Here’s a quick survey:
- Do you rate yourself as being well organised?
- Do you have a firm concept of the book in mind – what you want to say in the book (or what is its central theme) and what will readers takeaway from reading the book (or what will be its purpose or effect)?
- Is the content final (both text and images)?
- Do you have a lot of spare time, and an unlimited budget?
If you answered ‘no’ to any of the questions above the Waterfall methodology (our default way of working) won’t be ideal for you. If you answered yes to all, get ready for a successful project using Waterfall! If you are organised and like to plan things ahead, Waterfall will be just right for you.
Key features of our project management
Every Green Hill project has a dedicated project manager whose role is to maintain communication with the author and co-ordinate our production resources.
Surrounding this methodology is a well-developed technology. We use project management software that provides critical path analysis and deploys a Kanban. Project progress is monitored daily and managed accordingly. Proprietary manuscript preparation software and book design technology is used.
But it’s not just all about technology. Our project management methodology actually frees our accomplished team of book designers to do just that – design books. A creative studio that does not operate within a well-defined and structured project management system is often time poor. The creative staff – the book designers – have become so time poor trying to keep the project on track they don’t have time to design. At Green Hill our designers have time to focus on excellent book design, due to our project managers and project system methodology.
Back to contents