Experience sharing on how we in Scope Technologies have managed to make project management developer oriented or at least not painful for developer. Our project managers once allowed developers to organize project managements the way we developers want. What happened? How we’ve achieved minimization of administrative stuff? How we use GitHub.com as a tool for lazy project management. Sergejs is experienced .NET and WEB developer and team lead at Scope Technologies.

1. Lazy project
management

2. Me and Our Project

3. Lost
• Developers only team

4. Concern: Role separation
• Analyst
• Developer
• Tester
• Manager

5. Deploy it!

6. Per-Issue conversation
• Initial States: Open vs Closed
• Initial properties: Bug vs Feature
• More States and Properties
• verified,
• waiting,
• low-context,
• rejected
• duplicate
• question

7. Scrum VS Kanban

8. Estimations
• (9 = 1+3+5) NOT EQUAL (9 = 3*(~3))

9. waffle.io
• Kanban board for GitHub.com

10. Wiki
• If you want it to happen, write it down

11. Conclusions
• Kanban is natural for developers
• GitHub.com is enough for project management