{"action":"created","issue":{"url":"https://api.github.com/repos/ipfs/pm/issues/134","repository_url":"https://api.github.com/repos/ipfs/pm","labels_url":"https://api.github.com/repos/ipfs/pm/issues/134/labels{/name}","comments_url":"https://api.github.com/repos/ipfs/pm/issues/134/comments","events_url":"https://api.github.com/repos/ipfs/pm/issues/134/events","html_url":"https://github.com/ipfs/pm/issues/134","id":169469463,"number":134,"title":"Start weekly sprint calls with a short all-hands weekly call","user":{"login":"flyingzumwalt","id":138930,"avatar_url":"https://avatars.githubusercontent.com/u/138930?v=3","gravatar_id":"","url":"https://api.github.com/users/flyingzumwalt","html_url":"https://github.com/flyingzumwalt","followers_url":"https://api.github.com/users/flyingzumwalt/followers","following_url":"https://api.github.com/users/flyingzumwalt/following{/other_user}","gists_url":"https://api.github.com/users/flyingzumwalt/gists{/gist_id}","starred_url":"https://api.github.com/users/flyingzumwalt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/flyingzumwalt/subscriptions","organizations_url":"https://api.github.com/users/flyingzumwalt/orgs","repos_url":"https://api.github.com/users/flyingzumwalt/repos","events_url":"https://api.github.com/users/flyingzumwalt/events{/privacy}","received_events_url":"https://api.github.com/users/flyingzumwalt/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":17,"created_at":"2016-08-04T20:45:16Z","updated_at":"2016-11-10T02:08:00Z","closed_at":null,"body":"I propose a slightly different structure for the Weekly Sprint Calls on Mondays.  Could we discuss it on the upcoming call next Monday?\n\nThe proposal: \n1. Start with a short all-hands weekly call (aim for 30 minutes or less. Max 1 hour)\n2. Keep the Project-Specific sprint calls short and focused \n\nNote: _There are, of course, times when you need to have longer calls._ For example, it totally makes sense to schedule a longer Quarterly call to discuss the roadmap, and this might happen instead of that week's sprint call, but that should be treated as an exception and scheduled in advance so people can prepare for it.\n## The All-Hands Call\n\nPurpose of this call: Regular, Reliable, Short Call Where everyone who's committing on any repo under the IPFS umbrella checks in and has a chance to either call attention to particular items, to make announcements, or to seek discussion of a topic.  It's also a way for casual followers to get a high-level update on the pulse of the IPFS projects without having to follow all of the sprint calls.\n- Have an agenda for this call that people can add items to over the week. All agenda items need to have a person's name on them.\n- Have a moderator and notetaker. Rotate these responsibilities.\n- Open the meeting with a roll call\n- Ask if anyone has additional agenda items\n- Detailed discussions get redirected to the project-specific sprint calls, or to github, irc, etc. \n## The Project-Specific Sprint Calls\n\nIn short, avoid using these calls as a time for lengthy announcements or in-depth discussions.  Use them to discuss the tickets people are working on and to allow brief discussion of any relevant topics or blockers. If any topics require further discussion, redirect it to either a follow-up call (ie. \"Let's discuss this between the three of us immediately after the scrum.\"), irc, or to github issues.\n\nI propose the structure of Scrum Standup Meetings (or a loose interpretation of it) as a possible framing for these sprint calls.\n\nThis will only become really smooth when we settle on a [Project Management Process](https://github.com/ipfs/pm/issues/125#issuecomment-237547155) because a smooth standup call relies on having a consistent wall of tickets to refer to.\n"},"comment":{"url":"https://api.github.com/repos/ipfs/pm/issues/comments/259583048","html_url":"https://github.com/ipfs/pm/issues/134#issuecomment-259583048","issue_url":"https://api.github.com/repos/ipfs/pm/issues/134","id":259583048,"user":{"login":"RichardLitt","id":910753,"avatar_url":"https://avatars.githubusercontent.com/u/910753?v=3","gravatar_id":"","url":"https://api.github.com/users/RichardLitt","html_url":"https://github.com/RichardLitt","followers_url":"https://api.github.com/users/RichardLitt/followers","following_url":"https://api.github.com/users/RichardLitt/following{/other_user}","gists_url":"https://api.github.com/users/RichardLitt/gists{/gist_id}","starred_url":"https://api.github.com/users/RichardLitt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RichardLitt/subscriptions","organizations_url":"https://api.github.com/users/RichardLitt/orgs","repos_url":"https://api.github.com/users/RichardLitt/repos","events_url":"https://api.github.com/users/RichardLitt/events{/privacy}","received_events_url":"https://api.github.com/users/RichardLitt/received_events","type":"User","site_admin":false},"created_at":"2016-11-10T02:08:00Z","updated_at":"2016-11-10T02:08:00Z","body":"No problem. :) Thanks for asking! Looking forward to the PM document being worked on, too. "}}
{"actor":{"display_login":"RichardLitt"}}