1 of 13

BHL Project Management Playbook

People, Process, Systems

2 of 13

3 of 13

BHL Strategic Plan 2020 - 2026

Relevant Content: �Grow BHL into the most comprehensive, reliable, reputable repository of data-rich biodiversity literature, and other original materials, to support a response to global challenges.

Tools and Services: �Create services and tools that facilitate discovery of BHL content to improve research efficiency for all potential users.

User Engagement: �Increase global awareness about BHL and biodiversity issues to inform existing users and attract new user communities.

Partnerships and Alliances: �Grow BHL consortial partnerships and alliances to foster cross-institutional collaboration.

Mission Enabling: �Increase financial strength, effective administrative support, and organizational excellence to ensure BHL’s continued success.

4 of 13

Group Goal Mapping

5 of 13

Work Break Down

Goal 2.1 (d)(f)

Project

Component

Issue / Ticket

6 of 13

BHL-Wiki Charter - Our Goals

Maximizing the Accessibility and Interoperability of Biodiversity Data through Semantic Web Integration and 5-star open data, FAIR, and CARE Data Principles

Advancing Data Modeling Work to Support Global Challenges

Strengthening User Experience, Engagement, and Global Partnerships

7 of 13

Work Breakdown in Github

Project = Project is a collection of goals and tickets
Goal = a thematic collection of related tickets, in agile this is called an epic
Ticket = a work request written from the perspective of the user

Github

Project

Goal 1

Ticket 1

Ticket 2

Goal 2

Ticket 1

Ticket 2

Goal 3

Ticket 1

Ticket 2

8 of 13

Kanban / Scrum

9 of 13

User Story Template

10 of 13

A User Story in Github

11 of 13

Story Points

0	No effort. No business value is delivered. Might be a small lift like writing down ACTION items from a retro.	0 days, 1 hour or less
1	Extra Small. Requirements are clear, relatively easy task	1 day, 6 hours or less
2	Small. Team does similar tasks all the time. Requires a bit of thought, effort, or problem-solving. Considered low risk.	2 days, 12 hours or less
3	Average. Team has done a similar task before. Requires a some thought, effort, or problem-solving, maybe a few extra steps. Considered low risk.	3 days, 18 hours or less
5	Large. Complex work that hasn’t been done very often. Needs multiple collaborators and touch-points to figure out a solution. Medium risk.	5 days, 30 hours or less
8	Extra Large. Not done before. This task requires research and more than one resource to complete. Assumptions are made. High risk.	6 days, 48 hours or less
13	Warning! Very complex piece of work with a lot of unknowns and multiple assumptions, requiring more than one resource. Consider splitting.	10 days, 78 hours or less
21	Way Too Big. Break it down	15 days, 120 hours or less

12 of 13

Team Resources

Certifications

Dictionaries & Glossaries

13 of 13

Github Demo

https://github.com/users/JJDear83/projects/3