I promised a review of this to someone on Facebook, so I figured why not write about it here and get a 2-fer.
I currently track the majority of my magical stuff in a bullet journal style ephemeris. I know there are some very awesome magical astrological journals and such (like this gorgeous one by Benebell Wen) but for me, there's something important about having my own journal.
First, it's always going to be more accurate. I track some things that are either less common (thanks to Gordon I'm a Decan fan) or completely personal (like times when the current astrological alignments match my personal horoscope). Things that I don't care about don't get in the way. Plus everything is in my timezone.
Second, there's a real power to handwriting the information in. There's skin in the game and a sense of ownership of the book. Plus unlike digital solutions, it's a real world object, which is important in my very digital life.
Edited to add a list of all the posts in this series at the end...
This is reworked and expanded version of one of my early posts on Practical Magic Project Management: Agile Magic.
...In The Black Swan, our hero Taleb talks about the value of constant tinkering, failing fast, and shifting gears quickly. Our world moves very quickly, things change rapidly, and the best way to figure out what works is to fling a bunch of stuff at the wall and see what sticks.
Turns out that software development already figured this out and created a methodology to support it. It's called Agile Development and it's based on constant iterating, frequent feedback, and incremental change. It even has it's own manifesto that goes:
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 contrac…
Since I'm in the middle of flushing out the EBER project, I wanted to explain how I've been using the bullet ephemeris for project planning and management.
First, I created a main project page to capture the high level stuff:
Sorry for all the blank space, but it is a personal project after all.
I ended up using vision statements rather than a long narrative paragraph. This means that my vision statement sounds a lot like the kind of things I'd make sigils out of -- and don't think I won't take advantage of that.
I also very briefly outlined the first two main phases of the project, which are scheduled to take a year. Then I'll have a month long review / planning period to define and kick off year two. This is important for two reasons: one, the entire first year is focused on information gathering so I won't know what's next until I have more information and two, with agile planning I don't have to know everything in advance.