Muutke küpsiste eelistusi

Program Management for Open Source Projects: How to Guide Your Community-Driven, Open Source Project [Pehme köide]

  • Formaat: Paperback / softback, 175 pages
  • Ilmumisaeg: 06-Oct-2022
  • Kirjastus: The Pragmatic Programmers
  • ISBN-10: 1680509241
  • ISBN-13: 9781680509243
  • Formaat: Paperback / softback, 175 pages
  • Ilmumisaeg: 06-Oct-2022
  • Kirjastus: The Pragmatic Programmers
  • ISBN-10: 1680509241
  • ISBN-13: 9781680509243
Every organization develops a bureaucracy, and open source projects are no exception. When your structure is intentional and serves the project, it can lead to a successful and predictable conclusion. But project management alone won't get you there. Take the next step to full program management. Become an expert at facilitating communication between teams, managing schedules and project lifecycle, coordinating a process for changes, and keeping meetings productive. Make decisions that get buy-in from all concerned. Learn how to guide your community-driven open source project with just the right amount of structure.

Bureaucratic processes naturally develop in large organizations, and open source projects are no different. The trick is to keep the processes intentional and in service of the project. That's program management and you have probably been doing it even if you don't have that title. Make your open source projects successful, predictable, and enjoyable by applying the principles and skills of program management in this book.

See how program management differs from project management. Build trust and credibility by building relationships, sharing information, and communicating effectively. Construct efficient decision-making and governance structures, with openness and clear responsibilities. Conduct more effective and enjoyable meetings. Hold the right kind of meeting for the matters to be discussed: text, phone, video, or face-to-face. Develop release lifecycles, including release planning, schedules, and go/no-go decisions, and keep on schedule. Create and manage an effective changes process. Use your bug tracker to better understand and manage the bugs and feature requests of your project. Make decisions that get buy-in from all concerned.

Develop processes that serve your open source project instead of making the project serve the process.
Acknowledgments ix
Introduction xi
1 Manage the Program
1(12)
Take the Big Picture View
1(1)
Balance Priorities
2(4)
Manage Risks
6(3)
Report Status
9(1)
Do Everything
10(1)
Manage Single Points of Failure and Burnout
11(1)
Retrospective
12(1)
2 Zoom in on Projects
13(14)
Define "Project"
13(1)
Find the Balance
14(7)
Know the Artifacts
21(5)
Retrospective
26(1)
3 Communicate and Build Relationships
27(8)
Build Relationships
27(3)
Communicate
30(3)
Retrospective
33(2)
4 Make Good Decisions
35(8)
Define the Question
35(2)
Give a Voice
37(2)
Take a Vote
39(3)
Retrospective
42(1)
5 Design Suitable Processes
43(10)
Define the Context
43(3)
Build a Process
46(4)
Implement the Process
50(1)
Make Revisions
51(1)
Retrospective
52(1)
6 Hold Useful Meetings
53(18)
Why Bother?
53(3)
Schedule the Meeting
56(2)
Choose the Medium
58(5)
Make Your Meeting Productive
63(5)
Make Decisions in the Right Place
68(1)
Retrospective
69(2)
7 Develop Your Release Life Cycle
71(8)
Decide How Many
71(2)
Set the Phases
73(4)
Set the Length
77(1)
Retrospective
78(1)
8 Build a Release Schedule
79(20)
A Schedule's Purpose
79(2)
Choose a Schedule Model
81(1)
Define "Done"
82(3)
Add Milestones
85(8)
Manage Conflicts
93(2)
Keep the Schedule Accurate
95(2)
Communicate the Schedule
97(1)
Retrospective
97(2)
9 Manage Features
99(16)
Create a Template
100(3)
Set the Scale
103(1)
Set the Approval Process
104(4)
Create the Timeline
108(2)
Define the Life Cycle of a Proposal
110(1)
Shepherd the Proposals
111(2)
Retrospective
113(2)
10 Track and Triage Bugs
115(22)
Track Bugs
115(5)
Triage Bugs
120(4)
Prioritize Bugs
124(3)
Close Bugs
127(4)
Analyze Bugs
131(5)
Retrospective
136(1)
11 Ship the Release
137(12)
Set Release Criteria
137(5)
Freeze the Code
142(1)
Produce Release Candidates
142(2)
Determine Readiness
144(1)
Make the Decision
145(2)
Retrospective
147(2)
A1 Choose Your Tools
149(14)
Identify Your Requirements
149(3)
Pick Your Tools
152(10)
Retrospective
162(1)
Bibliography 163(2)
Index 165
Ben Cotton is the Fedora Program Manager at Red Hat. He has contributed to the Fedora Project and other open source projects for over a decade. Ben's career spans a variety of roles in the public and private sectors including system administration, software development, and marketing. He is an Open Organization Ambassador and a Opensource.com Correspondent alumnus. Ben holds a masters degree in IT Project Management from Purdue University.