a presentation on the one-person project management team. part of the "Project Management in Practice" pre-conference at Internet Librarian 2008.

1. one-person
the
project management team
Amanda Etches-Johnson, IL2008

2. project
management?
what do I know about

3. not much

4. one-person
the
project management team
• one-person project management?
• project management @ my library
• the context: my project
• challenges
• tips

5. {one person}
the
project team?

6. oxymoron
it’s an

10. projects
fail
one person
when they depend too much on

11. project managers
people
develop the
not the
thing

12. is it even
project
management
no team ?
if there’s

13. project
{
management }
@ my library

14. lots
of projects

15. varying levels of
PM training

16. no
enterpriseproject
management
framework (yet)

17. project management
on the fly

18. me
what does that mean for
as a project manager?

19. { context}
the

20. project
my
redesign the library website

21. redesign
the library website
• adopt the new campus brand
• implement a CMS
• ...just make it better!

22. the
timeline
• started in 2006
• really started in 2007
• really, truly started in 2008

23. the
timeline
go live? fall 2008

24. players
the
• advisory committee
• sysadmin
• co-op student
• me

25. { challenges}
the

26. project manager
a person responsible
for planning, executing,
and closing a project

27. project team
...works under a project
manager and consists of
various members with
responsibility for certain
aspects of the project.

28. sometimes you are
both

29. being
manager + team is hard
plan, determine
requirements, develop,
wireframe, build, user
testing, beta, launch, fix
bugs, document,
communicate throughout

30. being
manager + team is hard
managing expectations

31. being
manager + team is hard
where does the planning stop & the doing start?

32. {
tips to keep you
sane}

33. timeline yourself
• beware over-planning!
• timeline in 1-week chunks
• deadlines are your friend

34. best
practices still apply
• the project charter
- title
- synopsis
- scope
- dates
- resources
- stakeholders

35. best
practices still apply
• version control
- keeps you on track
- especially important for tech projects

36. best
practices still apply
• watch for scope creep
- stick to the plan
- more features = more time OR resources
(or both)

37. best
practices still apply
break the project into
manageable chunks

38. best
practices still apply
manage expectations

39. best
practices still apply
document

40. don’t
apply
some practices
Gantt charts

41. don’t
apply
some practices
complex PM software

42. advisory
use
that
committee
• advice!
• decision-making

43. working
groups
assemble
• deal with a specific issue
• short, firm timeline

44. everyone
project
is your
team !
don’t isolate yourself, don’t
get lonely, the whole library
can be your project team!

45. {questions?}
advice?
experiences to share?

46. {thanks!}
this presentation is online at
http://blogwithoutalibrary.net/talk/il2008/pm.pdf

47. image credits
• bicycles http://www.flickr.com/photos/prosto/1694841563/
• trophies http://www.flickr.com/photos/opticallyactive/212340456/
• framework http://www.flickr.com/photos/sifter/292158704/
• tightrope http://flickr.com/photos/schoppik/137915309/
• question mark http://www.flickr.com/photos/eleaf/2536358399/
• snowbirds http://www.flickr.com/photos/damclean/187056021/
• stacked snowbirds http://www.flickr.com/photos/fwp/49515622/
• gantt chart http://en.wikipedia.org/wiki/Image:GanttChartAnatomy.png