When I left off last sprint, I didn’t know exactly what the next chapter would comprise. You see, some scenes are important, a part of the plan from the beginning. Sometimes, however, you need to get a character from point A to point B. This was one of those latter weeks. I had a skeleton of an idea, but couldn’t figure out how to make it relevant. After three days of reflection, however, a stroke of inspiration hit! I have not finished the scene, but I seem to have gotten over that hump.
In the absence of actual writing, I found plenty to do to stay busy on my novel. I read through my existing work and edited it. I finally wrote down notes of future scenes and characters that have been swirling nowhere but my head. I also organized my ideas into a coherent whole, mapping the book scene-by-scene, so now I have an idea of how long the book will be and what scenes I still need to devise to fill the holes.
One useful tool I found is Aeon Timeline, a decent tool for developing multi-arc timelines for novels. By mapping out the events in my novel this way, I determined that some of my dates and times were impossible, and I was able to go back and fix them. It’s really easy to get lost in the flow of writing, so having a simple tool like this makes a big difference.
Finally, I’ve committed to using Scrivener to build the manuscript for my novel. It has its weaknesses, but it’s proven invaluable in organizing and building my project. I can even compile to formats readable on the Kindle and Nook.
I’d call this sprint a minor success. I’ve added about 5,000 words – less than half of the output of my last two sprints – but the organizational work puts me ahead in other ways. The entire book is now sitting at just under 30,000 words. With my new plan I think the end product will be somewhere between 100,000 to 120,000 words in length, so I’m making good progress towards my end-of-year completion date for the first draft.
Upcoming sprint: writing, writing, writing. I want to finish writing the current scene plus two more, comprising the next chapter. Fortunately, the next two scenes should be a little easier than the last one was.
What a great few weeks! I’ve been very productive this sprint, completing and editing two chapters. My current word count is ~22,000 – the average first-time writer’s novel runs around 100,000 words, or 300 pages, and that’s what I’m shooting for.
One large positive was that I changed software this sprint. I had used Open Office, a free alternative to Microsoft Word, but I was starting to have problems with organization. My chapters were in separate files, making it difficult to swap from one to the other easily, and my notes were all over the place. I am evaluating an application called Scrivener, which combines a decent editor with great organizational tools. It gives me tools for creating easily accessible notes for character, location and other things. It uses a hierarchical project list for chapters and notes making it similar to using a programming IDE (integrated development environment). It may not make me write better, but it allows easier access to all the elements of my story and helps me to organize things, and that helps me to write faster. I can concentrate on the writing. It has a few downsides – it uses a proprietary file format that I can’t view on my mobile devices. I can export files from it, of course, but that requires an extra step I shouldn’t have to take. It would be preferable if the elements were broken out into separate files. It also has a few bugs, for instance a crash when I tried to use the integrated thesaurus. I have a few other apps to look at before I decide, but I’ll probably buy the full version soon.
Another positive is that my first draft writing is getting better. I find that I have less editing to do the more that I write. This was, of course, expected, as the only way to get better at writing is to write.
I can’t think of any negatives this time, other than I wish I could write faster. There is only so much time I can spend, and I’m often stuck between writing my current chapter or organizing my thoughts on future chapters so I won’t lose them. Yeah, I know, first world problem.
Some random thoughts before I go:
- Wow, this book is really personal. I’ve distanced it enough from my life that it isn’t about me, but it’s what I could be. I don’t want to offend family or friends who think some character is them or modeled after them. It’s very hard to draw a line between something the story needs and the realities that drive my thinking. I guess what I’m saying is, I apologize in advance.
- For the first time since I started, I don’t have a clear idea of my next chapter. I have some rework to do – some of the later story is forcing changes in earlier chapters. I’ve got some planning to do, though, or I’ll need to work on the chapters out-of-order.
Onwards and upwards!
When I left off last sprint, I had been forced to go into a different direction with my novel. I had an interesting new idea but had not yet fleshed it out. For the first sprint of the new version of my novel, there were questions to ask. Could I develop a story around this idea? What work from the previous idea could be preserved, and what would would be lost? Could I fully engage myself in the reworked story? Was I on the right path? The answer to those last two questions turned out to be a resounding “yes”!
Before I could start writing, though, I needed to flesh out a story. I started by trying to retrofit ideas from my previous iteration into this one, but I could not find a way that didn’t seem awkward and forced. In the end, exactly NO writing I had done previously will be used in the new novel. None of my planned scenes will be in it as well. None of the names or other research will be relevant. In fact, of the content I’d worked on only one plot device remains – fortunately, the most significant one – and it has been reworked just a bit.
That is the bad news. The good news is, once I let go of the old story, the new story flowed out of me like water out of a cracked dam. I was able to take the skeleton of an idea and turn it into a fully flowing, plotted storyline with a beginning, middle and end, even if it’s not fully fleshed out. Knowing the direction, the words came easily. I have written nearly 8,000 words this sprint, completing the draft and first revision of the prologue and chapter 1. It is easily my most productive sprint so far.
What I have found is that this story is extremely personal for me, in a way the previous one could not have been. It is not dark like the former one; it has no violence, no disturbing imagery. It contains themes and plot devices that coincide closely with many of my chief interests: religion, science, science fiction, human nature and Asperger’s syndrome. It even contains a hint of romance. More importantly to me, I have never read or even heard of any novel remotely like what I’m doing.
I am extremely excited going forward, but I have a lot of work to do. Here are some of the things I need to keep in mind going forward:
- It’s great that my novel is so personal, but to be honest, I’m weird, and if it’s presented in too personal a way others will have trouble connecting with the characters.
- I have two main characters who are extremely similar. I need to ensure they each have a unique voice. That will take some tricky writing to accomplish.
- The science/science fiction elements are quite complicated, but I’m not writing (necessarily) for a science-literate audience. Can I explain things simply enough so that less technical people can follow the plot conventions, even if they don’t completely understand them? Can I do that without sacrificing the “real-ness” of the science fiction elements, as so many other authors do?
- The story is told in non-linear fashion, which makes it difficult for many audiences to follow. It is using a fairly unique plot device to deliver history, so perhaps it won’t be as hard to pull off.
Those are just a few of the issues I’ll have to deal with. I’m excited to start chapter 2 next sprint. I hope to have it, plus at least the first draft of chapter 3, done in two weeks. It should be no problem if I can be as productive as I was last sprint.
As far as the previous story – well, it’s on the shelf for now. Perhaps I’ll revisit it someday. Perhaps I’ll find some new way to deliver the plot that allows me to tell the story more uniquely. Doing things the Agile way may have provided some help here – it’s forced me to organize my information in a way that should be easy to recover in the future.
Back to writing!
This sprint was, most definitely, not a good one. There were some huge setbacks in my progress during the last two weeks, and I’ve gone through a range of emotions while dealing with them. I can’t say this is unexpected; in fact, I decided to use Agile partly because I knew there would be problems and I’d have to flexibly deal with them. I did not, however, anticipate issues of this magnitude, and it’s forced some serious re-evaluations of the entire project.
The sprint started off with my first bout of writer’s block. I had completed a scene – the first half of the chapter 2 – and needed to segue to the next scene that would finish it. For the life of me, I could not figure out how. My story had some very dark elements; however, I did not want the book to be overly dark. I had planned segues between dark scenes that would lift the mood and give the reader some respite before heading back into disturbing material. It was in these segues that I was having the most difficulty.
The second problem; I have had a name for my book since the very beginning. When I thought of it, I immediately did searches on Amazon and B&N and was pleased to see that there were no books using the name. However, I decided for some reason to google the term, and found it to be a term for a Mormon phenomenon; my target audience is Christian. I certainly don’t want to alienate Christians from reading my book and disappointing Mormons, so I moved my planned title to “working title” and created a chore to think up a new name.
The third problem, however, was terminal. As I’ve mentioned in earlier blogs, I got the original idea for this book in the mid-to-late 90’s, and had been working it in my mind since then. In the late 2000’s, a book was released that covered very similar territory, and it was a huge hit (selling millions of copies). At the time I was dismayed but felt my story offered a perspective that would offer a unique experience, and could stand on its own without appearing derivative. I had not revisited it since then, and had forgotten much about it. Something told me I needed to re-read it again to make sure that I was still veering clear of its territory, and to my horror, I was coming far closer to its tone than I’d planned. I think that I even inadvertently copied an element from that story. While I don’t think the idea needs to be totally unique, I do feel I need to justify it as a worthwhile venture for people to read. It was harder to justify now.
It took me about three days to walk through the stages of grief. At first, I thought I could just alter the story to avoid the areas that were too similar and concentrate on those elements that were unique. Well yes, maybe, but the problem is the areas of similarity were what made the character believable. I could not get my main character to where I needed him to be without going through where the other book’s main character went first. To accomplish what I wanted to do, it would require fundamental changes to the plot, main character, and even some of the scenes that I loved, and this would make the story fundamentally different.
So, I finally accepted this new reality and set my mind to reconsidering the story from the ground up. And I think I may have ended up putting together what may even be a better story than my original idea. It has most of the key, unique elements of the original. It does, however, follow a different path that is less dark, eliminates most of the disturbing imagery, and might actually even be a bit funny. I am constructing this story now; hopefully, I’ll have a solid plan after this next sprint and even some writing progress.
I am not giving up on the original idea. I have detailed notes and I may very well revisit it again in the future to see if I can find a unique way to present it. But, for now, it’s on the shelf.
- Make sure you do a Google search, at least, when coming up with a name or idea.
- Be familiar with popular literature in your field that is similar to your work.
- Don’t give up hope if you find you aren’t as innovative as you might think.
Back to the drawing board, but I’m still excited. I still want to have my first novel finished by the end of the year, and that goal is definitely not out of reach.
Well, it’s been two weeks since my last writing update, and I’m hopelessly behind getting part 3 of my Agile series completed. I do still plan on completing it, but am not sure when; thankfully, it’s my novel writing that is pushing it back.
A part of the Agile process is a “Sprint Retrospective”, where you look back at the last iteration to discuss what went right, what went wrong, and how things might be improved in the future. I plan on using these writing updates for that purpose; at the end of each 2-week sprint I will gather my thoughts and update my loyal fans (Hi mom!) on my progress.
I left the end of last sprint almost finished with chapter 1, having written about 5000 words total. This sprint, I finished chapter 1, reworked the prologue, and find myself about a third of the way through chapter 2. I have written around 2500 words this sprint; half as much as last time, but to be honest, the writing tasks were far more difficult. More on that later. I also thought up, spec’d out and created tasks for a few new scenes for later consideration. Finally, I identified new chores – writing related – that I need to work on to make my writing time go more smoothly.
- The first chapter consists mostly of dialog and setting up the plot devices that will be used throughout the rest of the book. The second chapter begins the meat, though; action, multiple settings and complicated descriptions. This writing is far more difficult.
- I find myself grasping for the words to describe the things in my head. I have tried online sources such as thesaurus.com and VisuWords, but have not yet found a good source for exploring word choices. One chore I’ve set for next sprint is to identify tools to help with words and phrasing.
- Describing things that exist only in your head is HARD. My novel contains elements of the supernatural, demanding descriptions of visual phenomena that are unique (as far as I know). It took four tries to get the first paragraph of chapter 2 to express the vision in my head correctly. Out of my five hours of writing this week, more than two hours were spent devising those 200 words.
- My book goes into some pretty dark places; I had to write a scene of cruelty and violence this week that is totally against my nature. My stomach churned and I almost felt like crying while writing the scene, and that shocked me., as I am not an overtly emotional person. I even tried to soften it up at times, but it made the scene less real; became obvious to me that I could not go halfway. The destination that I’m guiding the reader to – which is intended to be glorious – will lose its effect if the reader does not travel through the darkness. You must experience the pain to fully grasp the intended joy. I am nervous because this is only the first such scene I must write, and definitely not the darkest one.
- There is a constant need to “invent” things such as settings and characters. I have been going back through my own experience for this. I am worried about describing places or people that actually exist; the last thing I want to do is offend somebody. The strategy I’m using is to merge characteristics from two or more things to make them unique. For example, one extremely unpleasant character was constructed using attributes from three people from my past, none of whom is unpleasant. If I finish this book and somebody thinks a character is them, two things: 1) it might be a little, and 2) it’s not you!
I’m not sure how much writing I’ll get done in the next two weeks. I’ve allocated 10 hours per two weeks so far; I worked about 10 hours the first spring and 6 hours this sprint (so far, I may not be done for the day). I won’t ascribe an official velocity – the amount of time I am able to finish per sprint on average – until after the next two sprints. I’m hoping I’ll discover a better rhythm by then.
I have not yet written the third part of my “Writing Fiction with Agile” series, and may not for another week. I’ve chosen a tool and will likely use it to illustrate the principles I spoke of in parts one and two; however, I’m hoping to find a tool that I can better tune to my needs. I’ve evaluated three software solutions so far, but all have proven less apt than the original.
As far as writing my novel is going, I am happy to report success! I was able to get into the “writing zone” this weekend and spent 6 hours writing about 5,000 words. I am almost done with chapter 1; it will obviously need some rework and editing, but I am very pleased with the overall structure and content.
The big question is, has Agile helped me? I spent part of my first sprint putting my ideas into my selected software tool (Pivotal Tracker), estimating the time of each task, and prioritizing the work. I’ve noticed some benefits already:
- I had an idea of what I wanted to do with chapter 1, but it was incomplete. By breaking my work down into smaller tasks, I was able to identify another, previously unrelated, scene that fit well here. With a little rework I was able to use it to completely flesh out the chapter. I might have never noticed this connection otherwise.
- By breaking out small, non-writing tasks as chores, I was able to take the time to focus on them and get them done. There were three main characters and I had not decided on a name for any of them. I set up a task to find a name for each, and with 20-30 minutes of focused effort on each, I was able to come up with names that are meaningful and I’m pleased with.
- By prioritizing my stories, I found I was able to focus better on the task at hand. There are scenes that I am excited to write; I’d often find that I’d flit from one scene to another as I was thinking through the story, preventing me from focusing on getting one single task done. After prioritizing I found it easy to make myself think about completion of the immediate goal and put those other scenes on the back burner.
All in all, I’d say that Agile methodologies have been valuable. The goal is to get my writing done, and as long as they encourage and motivate me to do that, I will stick with them.
In my previous post I spoke of my desire to be a writer, and my trouble with fitting writing into my schedule. I presented Agile methodology as a possible solution to this problem. I will attempt to explain myself here more fully.
First, though, I want to stress that I understand that no tool is going to get a novel written. In the end, if I am successful it will be because I sat down and wrote it. What this tool might help me with is to break up my writing tasks into smaller, more manageable pieces; when I have time, whether it be an hour or many hours, I will be able to find work that needs to get done that can be completed in that time frame. The trick will be to break each major task out into discrete pieces, and document each piece enough so that I can complete the work when necessary. As I complete more and more tasks I will be able to build paragraphs and chapters from those pieces, and eventually piece the entire book together. By breaking down tasks this way I will be able to identify things I can do in smaller increments of time – an hour here and there. Tasks that can be started and finished discretely with lesser need to be in full-on “writing mode”. At least, that is the plan.
It should also be noted that I’m only utilizing a small subset of Agile methodology. It is designed for larger-scale projects among groups of teams, and most of its particulars have little relevance to my problem.
To start: Agile methodology defines its individual tasks as “epics” and ‘stories”. An epic is a large picture issue, such as a new product feature, while a story represents a sub-task contained by the epic. A story can be a “feature”, meaning a new piece of functionality; a “chore”, meaning rework or refactoring of existing functionality; or “bug”, a problem with existing functionality that needs to be fixed.
The structure of my novel is of a present-time dialog intercut by scenes from the two main character’s lives. Each character’s scenes build that individual’s overall storyline. The scenes are not necessarily told in linear fashion, but in a logical progression. Each scene will be complete in and of itself but will either present or build on vital information for/from other scenes. There is also a character who acts as a semi-narrator, moving the plot forward in the segues in-between scenes.
I will map these ideas into fiction writing by defining them as follows:
- Epic: I will define at least four epics, two being a single character’s storyline and a third to represent the segue scenes connecting those scenes. I will also write an epic to represent the research that needs to be done to make my characters, plot and scenes believable.
- Feature: this refers to an individual, unwritten scene within an epic.
- Chore: this will refer to tasks such as researching a topic or going over a chapter or story that has been edited.
- Bug: this refers to the editing of existing content when I feel it is not yet up to par. I will also use them to refer to other rework issues, such as continuity issues or where a scene’s worthiness needs to be re-evaluated.
Also a part of Agile is the estimation of the time required to complete each story. This is usually done by taking some number system – say 1, 2, 3, 5, and 8, and rating each story one of those numbers. The actual time each represents depends on the length of a sprint (I’m setting mine to 1 week) and the discretion of the project manager. For this project, I’m going to enable 8 possible settings – the numbers 1 through 8 – where each represents an hour of my time.
Ideas for features, bugs and chores will be placed in a queue called the “icebox” initially. When I decide that they are actual tasks that I want to complete, they will be moved into the “backlog”. Projects that are to be worked on in the immediate time frame will be placed in the “current issue” queue.
Finally, I will define each sprint (iterative time frame for planning) as a period of two weeks. I will decide at the beginning of each sprint how many points I can complete in the next two weeks based on my knowledge of my schedule during that time. Based on that number, I will move items from the backlog into the current issue queue for me to focus on. Of course, if I find that I can do more than planned I can always pull stories from the backlog.
At this point, all of the information above is fairly theoretical. Next post, I choose a software tool to manage these stories, and discuss how I will use that tool.