Skip to main content

Large Scale Digitization Projects Part 2: Project planning

Project planning and project management can be useful for many things besides digital projects, however they are particularly useful for digital projects because digital projects tend to have many different components. You have to worry about people, funding, schedules, and technology. Any one of those things by themselves would be difficult to manage without a plan of attack. Dealing with all of them at once requires a lot of attention and planning.


Project planning and project management can be summed up in 5 steps. These should be done in order. This is a brief overview of the project process, and by no means does it cover the whole topic. If you are interested in reading more about project management, I highly suggest The McGraw-Hill 36-Hour Project Management Course by Helen S. Cooke and Karen Tate (ISBN 0-07-143897-1).


1) Context
Once you have been assigned a digital project, develop your context. Why is the project important? Who wants it done? Who is involved and why? Write down the context of the project (Who, what, where, when, how and why).

2) Estimate work
Once you have your goals for the project, and your affected parties, you then need to estimate your work. This consists of developing tasks that need to be done, defining who will do the task, and getting that person to define how long it will take them to do that task. You may be able to say a project will take you a year, but you won’t know for sure until you know how long each individual task will take you. Write out the tasks, their durations, and make sure to note what tasks are dependent on other tasks.

3) Get it approved
Take your context document and your work estimate document to the person who assigned the project to you. Make sure they understand how much the project is going to take (time and money). They may decide that it’s not worth it. However, if they decide it’s worth it, then it’s time for project implementation.


4) Manage scope, schedule, and resources
During project implementation, your job is to make sure everything is in scope, in schedule, and under budget. You manage your scope (what the project entails), by keeping a close eye on your schedule and resources. If you suddenly need more or less time or resources, that’s an indication that your scope has changed. To manage schedule, you just have to make sure that tasks are starting and finishing on time. If one task is late, it may push other tasks back. To manage resources, keep an eye on your budget and your schedule. If your schedule is getting pushed back, you may need more people (which may mean you need more money).


5) Closeout
Before a project is done, you must close out the project. Go to all the people who wanted the project to happen and verify that they are happy with the product. Think of it like a business asking their customer if they were happy with the experience. Then, you can collect any project documentation, make note of any lessons learned, and archive the documentation somewhere that future project managers can access it.

Comments

Popular posts from this blog

Documentation and Good Management in Digital Libraries

This month is all about self-evaluations for me and my employees.  Because of this, I have been thinking about how a manager is supposed to show their work and their worth. The easy answer is to say that if the employees are doing well, then the supervisor is good. It could be that the employees are doing well despite a bad supervisor. An employee doing badly is also not a sign of a bad supervisor. So what tangible thing can I say makes me a good or bad supervisor? Throughout the year, I try to focus on the actions I take to make my employees' lives at work better. I try to give them direction, advice, and help make things easier. I also try to champion them. Things do not always work but I adjust. When I sit down to write my own evaluation, though, I end up writing about documentation. To me, that is a concrete indicator of a good supervisor. They care enough about the work, and their employees, to write things down and make a record. I want to challenge everyone to write

Bureau of Indian Affairs- Digital Collection

The Bureau of Indian Affairs is one of the oldest Bureaus in the United States.  It was established in 1824 by Secretary of War John C. Calhoun . While the history of the organization has been controversial, their records are open to the public.  This collection brings together letters distributed from the Bureau of Indian Affairs starting in 1832 and going on into 1966. View the rest of the collection:  http://bit.ly/2h0hKvW 

The Workload Iceberg for Digital Collections and Initiatives

In the last few weeks, I was asked to write a small paragraph explaining my area to others in the library.  I was happy to do this, as many people say they don’t know what my people do.  It’s sometimes hard to explain to others what we do without going into overtly technical topics and terms.  If we have done our job right, we’re practically invisible, which is the way it should be.  Anyway, writing the description made me realize why there is often a mis-match between what we do and what people think we do.  I’ll let you read the description yourself.  I’ve underlined the important bit. “Digital Resources is primarily an Open Access publisher.  We publish both born digital items (produced by students or faculty), and we scan to publish or republish old items. We curate digital collections through the whole digital life-cycle. Our work is a bit different from other departments because the more work we finish; the more work we create in having to maintain the collections. We’re no