JournalPRODUCTION BUILD

A time machine for project work

While arranging documents for Article Studio, another studio almost appeared. Project Studio. Apparently, available space in this house is still not exhausted :-) At work I develop an internal project management platform. It leans on IceScrum, with course towards standing on its own in following months. Releases, sprints, features, epics, stories, tasks... I spend enough time with those ideas to bring some of them home, whether invited or not. But here I work in bursts. Something catches me, I follow it, then pause and do something else, also cool. A cycle measured in fixed time does not tell much about that. I can name outcome I want, though. Let that period last until we reach it, or decide that we want something different. I imagined project as time machine. Vision is somewhere in future. We bring part of it closer by deciding what to build, then how, until there is something we can do now. We work, and what is finished moves into past with evidence. What did we actually make? How did that differ from plan? Why? There should be room for all that without making present hard to find. First proposal had vision, plan and history under documentation. Close, but not quite. Documentation should tell someone what project is today. Vision is one document. How we work is another. Architecture, data conventions, whatever other aspect deserves explanation... open docs folder and find current knowledge. Work has its own place. To do, in progress, done. In to do we already recognize that something is needed, and can develop scope and approach before touching implementation. In progress means it has started to materialize. A pause between bursts does not send it back to beginning. Done keeps outcome and evidence, and can grow as much as needed. One counter for all items. I do not want to decide whether something is story or task before I know what it involves. An item may become one small change, or need splitting several times. Keep its number, link the pieces, let actual work show its size. Even a plan can be an item. It starts from some reference in vision, gets scope, enters work, branches if needed, and closes when its milestone is met. Remaining pieces need an explanation; finishing a chapter does not make unfinished things disappear. Vision changes too. I first thought we could save snapshots at milestones, to look back after years and compare future we imagined with what arrived. Then... this is Git already. Article Studio itself can have history, not only its content database. No need to make history folder for every living document. Meaningful commits can mark those moments. We arranged it and recorded work already done. Retrospectively, clearly saying so. No pretending that numbered plan existed yesterday just because we have one now. That is enough Project Studio for today: some folders, records, and a way to move. We can learn if it fits while doing the work it is meant to hold.