{"action":"created","issue":{"url":"https://api.github.com/repos/kbase/project_guides/issues/57","labels_url":"https://api.github.com/repos/kbase/project_guides/issues/57/labels{/name}","comments_url":"https://api.github.com/repos/kbase/project_guides/issues/57/comments","events_url":"https://api.github.com/repos/kbase/project_guides/issues/57/events","html_url":"https://github.com/kbase/project_guides/pull/57","id":110740948,"number":57,"title":"[WIP] Remaining questions from previous PR","user":{"login":"fperez","id":57394,"avatar_url":"https://avatars.githubusercontent.com/u/57394?v=3","gravatar_id":"","url":"https://api.github.com/users/fperez","html_url":"https://github.com/fperez","followers_url":"https://api.github.com/users/fperez/followers","following_url":"https://api.github.com/users/fperez/following{/other_user}","gists_url":"https://api.github.com/users/fperez/gists{/gist_id}","starred_url":"https://api.github.com/users/fperez/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fperez/subscriptions","organizations_url":"https://api.github.com/users/fperez/orgs","repos_url":"https://api.github.com/users/fperez/repos","events_url":"https://api.github.com/users/fperez/events{/privacy}","received_events_url":"https://api.github.com/users/fperez/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-10-09T21:44:40Z","updated_at":"2015-10-13T22:12:14Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/kbase/project_guides/pulls/57","html_url":"https://github.com/kbase/project_guides/pull/57","diff_url":"https://github.com/kbase/project_guides/pull/57.diff","patch_url":"https://github.com/kbase/project_guides/pull/57.patch"},"body":"Note, the body of the PR is not really meant for merging as-is, only to record the start of the discussion.\r\n\r\nThese are a few questions that arose in the previous PR #55, regarding how the Agile\r\ndevelopment process and decisions are made.  \r\n\r\nI wanted to make sure we didn't drop them, so we can clarify them, even if in the end, this document isn't the final place to discuss them all.\r\n\r\n1. A request for more transparency from EC on decision process: agenda and\r\n  outcomes, as they pertain to the development process, should be shared with\r\n  the team.\r\n \r\n1. How is work outside of the sprint cycles reported, managed, or decided on? \r\n\r\n1. Does the Executive committee review work that is not part of the sprint\r\n  cycles? \r\n\r\n1. How do the working teams get a finer-granularity and updated description of\r\n  priorities and project vision? This seems critically necessary to have clear\r\n  objectives and goals that to plan against.  Basically, a dynamic, living\r\n  version of the project high-level roadmap that is updated periodically by the\r\n  EC."},"comment":{"url":"https://api.github.com/repos/kbase/project_guides/issues/comments/147868902","html_url":"https://github.com/kbase/project_guides/pull/57#issuecomment-147868902","issue_url":"https://api.github.com/repos/kbase/project_guides/issues/57","id":147868902,"user":{"login":"aparkin","id":7152836,"avatar_url":"https://avatars.githubusercontent.com/u/7152836?v=3","gravatar_id":"","url":"https://api.github.com/users/aparkin","html_url":"https://github.com/aparkin","followers_url":"https://api.github.com/users/aparkin/followers","following_url":"https://api.github.com/users/aparkin/following{/other_user}","gists_url":"https://api.github.com/users/aparkin/gists{/gist_id}","starred_url":"https://api.github.com/users/aparkin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aparkin/subscriptions","organizations_url":"https://api.github.com/users/aparkin/orgs","repos_url":"https://api.github.com/users/aparkin/repos","events_url":"https://api.github.com/users/aparkin/events{/privacy}","received_events_url":"https://api.github.com/users/aparkin/received_events","type":"User","site_admin":false},"created_at":"2015-10-13T22:12:14Z","updated_at":"2015-10-13T22:12:14Z","body":"@mlhenderson I think I need to work these through with you. I am not sure all of what is being requested. \r\n\r\nA request for more transparency from EC on decision process: agenda and\r\noutcomes, as they pertain to the development process, should be shared with\r\nthe team.\r\n\r\n--> Right now It is still unclear that the exec IS making any decisions. The ideally we would start with the diagram in the proposal and sprint proposals would line themselves up with boxes on that diagram \r\nThe EC would then evaluate whether each sprint actually did meet that box goal; if it was a signifcant priority compared to others; and rate it against thing that come up that are \"surprises\" that need to be dealt with. At the moment there is also always resource issues: we have to balance user growth with needed development and individual team interests and talents and it makes some decision making difficult. \r\nBut if we could create such a clean document the decision making proccess could be more transparent. \r\n\r\nHow is work outside of the sprint cycles reported, managed, or decided on?\r\n\r\nTheoretically I think all projects should report on the sprint cycle directly. All should be using GitHub (this IS outlined in the process guide) and decisions are made by a similar process as sprints but on a different time scale. \r\n\r\nDoes the Executive committee review work that is not part of the sprint\r\ncycles?\r\n\r\nYes, \r\n\r\nHow do the working teams get a finer-granularity and updated description of\r\npriorities and project vision? This seems critically necessary to have clear\r\nobjectives and goals that to plan against. Basically, a dynamic, living\r\nversion of the project high-level roadmap that is updated periodically by the\r\nEC.\r\n\r\nWell-- the EC relies in part on the team to help us make this finer-granuarity. We have a self-consistent field to come to.. we want: better documentation, more user testing, easier development, more functionality, better rendered current functionality, more responsiveness of the system; more data types; etc. We have no magic formula to figure out how to array resources to meet these goals and prioritize from the top because whatever I or others on the EC might thing we might not have the immediate resources who are interested/willing/able to do X especially when Y is also a priority. But I think if we can get the Jira system set up to respect the roadmap I talked about above-- and we can break that roadmap into slightly finer granularity (e.g. UE discussing the need for narratorial development, etc.) then I think this can become easier. \r\n\r\n"}}