Re: [Snowdrift-discuss] Implementing Holacracy -- TODO's inside
>> Implementing it here at Snowdrift.coop has been on the to-do list for a >> while, It has? Where is this TODO list that this item is on? Holocracy is a major shift in how things get accomplished. I’m not entirely sure if it’s appropriate at such an early stage , especially when things are just getting started and coalesced. It seems like the structure is already pretty well aligned with holocarcy. I’m not sure that a formal implementation would be helpful, my gut reaction is that it would be harmful. From: Stephen Michel [mailto:stephen.mic...@tufts.edu] Sent: Thursday, March 3, 2016 10:57 AM To: General discussion about Snowdrift.coop Subject: [Snowdrift-discuss] Implementing Holacracy -- TODO's inside Holacracy is an alternative organizational system to a traditional management hierarchy. Implementing it here at Snowdrift.coop has been on the to-do list for a while, and now that we're finally getting organized about how we're doing things, it's happening! I'm currently taking the lead on it but it would be really helpful to have another person who became a Holacracy expert, and could share facilitation duties. Our next step is to schedule our first governance meeting. I don't know how long it will take, but since it's our first and we'll be learning Holacracy's process in addition to the initial setup of everything, I'd like to try to block out 3 hours. Not everybody needs to be there for the whole thing (although that's preferable), but at some point, we do *need* myself, wolftune, salt, mray, and chreekat. (do y'all prefer I use your irc nicks or your full names?). Can somebody (wolftune, chreekat?) take the lead on this? There are two things that can make a Holacracy meeting successful; either can make up for the other: the people in the meeting being good / practiced at holacracy, and a good facilitator. I'm going to do my best to facilitate well.. and I'd also like to hedge my bets. If you're planning on attending, I'd like you to: Check out Monday's minutes. They're useful even if you were in the meeting -- I edited them to be much more clear. http://shovel.snowdrift.coop/meetings/28 Watch these videos. They're pretty understandable at 1.25x or 1.5x speed. As usual, 2x is a stretch, but do-able: [2 min] https://www.youtube.com/watch?v=MUHfVoQUj54 [18 min] https://www.youtube.com/watch?v=tJxfJGo-vkI [34 min; just watch 24:30-58:38] https://www.youtube.com/watch?v=zGLJRpAKS6E Also, please think about what your CURRENT *ongoing* responsibilities are and come prepared with those. A reasonable litmus test for "is it ongoing" is "does it start with a -ing verb?" Cheers, Stephen Totally not required, but if you have a particularly large amount of time on your hands, this is another useful one, starting at 12:15: https://www.youtube.com/watch?v=GoQU9FcE2NI Aaron -- if you can come with a signed copy of this, with yourself as lead link: https://github.com/holacracyone/Holacracy-Constitution/blob/master/Adoption%20Declaration%20Sample.pdf ___ Discuss mailing list Discuss@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/discuss
Re: [Snowdrift-discuss] organizing major Snowdrift.coop projects
In redmine I'm something of a sub project fiend. They are incredibly useful. Like anything, they can be overused/abused. -Original Message- From: Aaron Wolf [mailto:aa...@snowdrift.coop] Sent: Wednesday, March 2, 2016 11:55 PM To: discuss@lists.snowdrift.coop Subject: [Snowdrift-discuss] organizing major Snowdrift.coop projects Question I want answered ASAP: Do we want to make separate Open Project "projects" (perhaps as nested sub-projects) for the legal/co-op stuff, the CiviCRM/community-networking stuff that Salt is handling, and maybe other really distinct areas of work? If we do that, we should embrace it and start using OpenProject and meetings there and whatever to organize the tasks. Otherwise, we should clarify how we are going to keep track of these various areas of work. -- Aaron Wolf co-founder, Snowdrift.coop ___ Discuss mailing list Discuss@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/discuss
Re: [Discuss] on prioritizing next steps for Snowdrift.coop
I like the idea of the MVP being snowdrift.coop (as a project) on the snowdrift.coop (platform) being a working project. You don't need introductory material, you don't need anything else except functionality. MINIMUM MINIMUM MINIMUM Viable Product. Minimum being the key word. Design it for yourselves, you already know what is wanted/needed. Once you have snowdrift.coop working as a project and bugs worked out etc, than iterate into expanding into a couple other projects etc. At least that is a method that's worked for me. ___ Discuss mailing list Discuss@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/discuss
Re: [Discuss] on prioritizing next steps for Snowdrift.coop
Before you dive into process for process sake and die a death of a thousand cuts by the toolchain... How about a vastly simplified approach (can still use the tools of course but in a more streamlined fashion) 1) Define core personas. (project patron, project contributor). 2) Define what an minimally viable product would be for those two personas. 3) Spend three weekends (and 3 hours per day between weekends) building the minimally viable product. If it's more than a man month, kill it. Aggressively fight scope creep etc. (repeat the above for the corporate entity as well). Make that your first milestone. Make each of the three items an epic. I'm seeing lots of massive brain dumps, grandiose plans, long lists. That's a huge amount of information. You'll die from analysis paralysis. I used to do that as well (in my earlier investor/founder experiences). None of those ever shipped or even came close. With my current portfolio, we have followed the above process, and it's working incredibly well. FNF can easily be the first end to end customer for the MVP , at somewhat significant scale as well. (To all, I'm using lots of business/corporate/startup terms, that's where I live and what I do (quite successfully as an investor/founder/board member of several startups), but I'm also the co founder of a 501c3 (FNF https://www.thefnf.org) and a huge believer in the snowdrift mission etc. I've spent extensive time with the founders and core team and am providing an advisory role). See I was thinking that the redmine/agile/persona/mvp process was going to be like ~3 days (say Monday to Friday after SCALE). It's been almost a month since SCALE. (yes everything takes 3x and costs 5x of estimate). Still, keep it simple/lean and get something built. You've got a very solid sw eng/design team. Go build awesome. Do the legal entity in parallel. Please please please please read http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ and then read it again. Without a 0.1 , you'll never be successful. OpenProject let's you switch from cathedral to bazaar at any time. Heck just leave everything public, if anyone cares enough, they'll get in touch via a myriad of methods (5 mailing lists? Really? That's a bit much in my opinion). ___ Discuss mailing list Discuss@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/discuss
Re: [Discuss] OpenProject Work Packages Workflow
On 2016-02-11 15:25, Stephen Michel wrote: On Thu, Feb 11, 2016 at 2:49 PM, Bryan Richter wrote: On Wed, Feb 10, 2016 at 03:15:38PM -0800, Stephen Yeung wrote: Regarding Milestones they're generally meant for big events (i.e. launches or when you complete a suite of inter-related features) wherein you take stock and review work and see if changes are needed. Right now our two "milestones" are: Alpha: complete website with funding mechanism (but no real money) Beta: Real money!! After that there's a lot of directions we can go, i.e., we'll need to take stock and review. Does anyone have feeback or questions on these two milestones? Feedback, yes. I'm not sure if we should call these milestones, but I think there are several important big events: Pre-Alpha (name?): complete site except funding mechanism, where hitting the 'pledge' button signs you up for the 'announce' email list. - Primary required work: UX & implementation Yes. This is a good approach. It's what my team has done with rackrental.net. Though we just have a free tier that the invited users are in. So site and app are functional but no real money yet. Alpha: Self funding: Real Money, only one project -- snowdrift.coop, mostly-complete mechanism (doesn't need to account for multiple projects), - Primary required work: mechanism, legal, ongoing UX Yes. People have to see that money can move through the system, some people have contributed, features work etc. Closed Beta: all of the above plus complete funding mechanism, invite exclusively popular FLOSS - Primary work required: mechanism, legal, outreach, ongoing UX Yep. I like the term early access, advanced placement etc. Beta is too overloaded. Open Beta: self-explanatory - Primary required work: outreach, ongoing UX Stable At each stage we should re-evaluate our priorities, so the farther down you go in that list, the more tentative. !DSPAM:56bcfc36244981056110400! Yep. Plans of mice and men etc... ___ Discuss mailing list Discuss@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/discuss
