It will be interesting to see what happens when this does grow bigger. Hangouts only supports us to 10 participants. I think that it might be important that folks always RSVP to meetings when we schedule them so that we get a good head count in case we need to figure out an alternative to Hangouts.
On Mon, Nov 23, 2015 at 5:17 PM, Ted Wilmes <[email protected]> wrote: > This was a good experience for me. I felt like I was able to soak in some > more of the breadth of what is going on. I could see this one mega meeting > untenable at a certain team size but as long as it was, I usually lean > towards one uber meeting to knock things like this out vs. a smaller weekly > one. And yeah, maybe as us new folks get up to speed, we can provide more > help tagging things release wise. Possibly even coming up with a first cut > before the meeting so that the meeting itself really focuses on the > communication and then making any adjustments based upon other folks' > perspectives. > > --Ted > > > > On Mon, Nov 23, 2015 at 2:28 PM, Marko Rodriguez <[email protected]> > wrote: > > > Hello, > > > > So this is the 3rd time we have done the "post-release JIRA > > review"-session. This was our largest group yet -- Stephen, Marko Daniel, > > Ted, Jason, Dylan. Given the full house, I would like to know if people > > like this model and if they have any recommendations to make it better? > > > > Here are my thoughts: > > > > 1. [POSITIVE] I like that we clean house by going through each > > ticket and dealing with it. Not just letting things sit forever. > > 2. [POSITIVE] I like that we get specific on who does what and > for > > what release. Commitment is good to keep things moving. > > 3. [NEGATIVE] It took us 2.5 hours to go through all those > > tickets. Its not THAT bad, but its a long meeting. > > 4. [NEGATIVE] It was primarily Stephen/Marko talking… Lots of > > people are new so its hard to know what lots of these things are. > Hopefully > > this will change with time. > > > > What are others thoughts? > > > > Thanks, > > Marko. > > > > http://markorodriguez.com > > > > >
