Church Rock & Roll Out Plans

Question

1

Church Rock & Roll Out Plans

Derek Dalton posted 9 Years Ago

I am enquirying of the churches, (specifically CCV) who have or are currently rolling/rolled out Rock. Would you post any documentation of how you rolled out Rock to your staff, volunteers, and members.

IE.(Things we are considering)

I.   Pre-deploy
   A.   Announcement – concentrate on what's in it for them
   B.   Documentation
       1.   Description of what's coming
       2.   Schedule of deployment
       3.   Schedule of training
   C.   Testing in our environment w/full database
   D.   Roll-back plan
   E.   Training plan
       1.   Develop trainers
       2.   Pilot (same Ministry Department)
       3. Deployment
       4.   Follow-up
   F.   Follow-up plan
       1.   Training
       2.   Support

II.   Deploy
   A.   Pilot deployment? (Pilot deployment is migrating Rock incrementally by ministries.)
   B.   Phased deployment? (Migrating Rock incrementally by modules.)
   C. Big Bang deployment? (Complete and simultaneous implementation of Rock across the church.)
   D. Parallel deployment? (Running both ChMSs until implementation of Rock is considered to be complete and successful.)

III.   Training
   A.   Brown-bag lunches
   B.   Webinars
   C.   Systems support
   D.   Admin support

IV.   Follow-up Support
   A.   Help desk (telephone or email)
   B.   User guides
   C.   FAQs
   D.   Follow-up training

Thank you in-advance. I understand if you are in the middle of rolling out Rock (or IT on staff at a church :) ), you are probably trying to keep your head above water.

Derek

Arran France · Answer 1 · 2015-06-26T06:57-07:00

0

Arran France replied 9 Years Ago

This is a really great question and I've been thinking of compiling information about how people have done training and deployment to produce resources to help people make the switch.

I had a long edit here with some thoughts but I managed to Ctrl+W away from it!

Here's a shorter version:

Have a fairly rapid process for escalating potential bugs as they're definitely there but can appear like user error.
Our training flow was: basic user information -> tags and relationships -> groups -> data views -> reporting -> communicating
For us it made sense to transfer the bulk of our day to day over to Rock at once as in terms of 'modules' Rock is fairly synergetic. A couple of ministries had strong processes already but they're being absorbed into Rock now. We also avoided transferring our forward facing site initially and got away with fairly basic 'micro-sites' for our volunteers.

Edit Answer

<p>This is a really great question and I've been thinking of compiling information about how people have done training and deployment to produce resources to help people make the switch.<br />
<br />
I had a long edit here with some thoughts but I managed to Ctrl+W away from it!<br />
<br />
Here's a shorter version:</p>

<ul>
	<li>Have a fairly rapid process for escalating potential bugs as they're definitely there but can appear like user error.</li>
	<li>Our training flow was: basic user information -&gt; tags and relationships -&gt; groups -&gt; data views -&gt; reporting -&gt; communicating</li>
	<li>For us it made sense to transfer the bulk of our day to day over to Rock at once as in terms of 'modules' Rock is fairly synergetic. A couple of ministries had strong processes already but they're being absorbed into Rock now. We also avoided transferring our forward facing site initially and got away with fairly basic 'micro-sites' for our volunteers.</li>
</ul>

<p>This is a really great question and I've been thinking of compiling information about how people have done training and deployment to produce resources to help people make the switch.<br />
<br />
I had a long edit here with some thoughts but I managed to Ctrl+W away from it!<br />
<br />
Here's a shorter version:</p>

<ul>
	<li>Have a fairly rapid process for escalating potential bugs as they're definitely there but can appear like user error.</li>
	<li>Our training flow was: basic user information -&gt; tags and relationships -&gt; groups -&gt; data views -&gt; reporting -&gt; communicating</li>
	<li>For us it made sense to transfer the bulk of our day to day over to Rock at once as in terms of 'modules' Rock is fairly synergetic. A couple of ministries had strong processes already but they're being absorbed into Rock now. We also avoided transferring our forward facing site initially and got away with fairly basic 'micro-sites' for our volunteers.</li>
</ul>

Save Cancel

Ken Roach

9 years ago

Great, Arran. Did you develop any training documentation?
Arran France

9 years ago

Hey Ken,
I have rough handwritten notes (I delivered all our training) and I may be able to dig up some Powerpoints to go with them but nothing reusable in its current form. If there is genuine need I may be able to craft something generic but it may well be that this is something that could be fed into from multiple churches and licensed under CC. Thoughts?

Ken Roach · Answer 2 · 2015-06-27T03:34-07:00

0

Ken Roach replied 9 Years Ago

Hi Derek. This is very valuable thinking. I'm working in a Government department at the moment on a software implementation project and see again the importance and value of having properly thought through transition plans. Most smaller churches, I'm guessing, don't have time or don't have the expertise to do this. If 'we' could put something together than was generic enough for others to use it would be very valuable, and appreciated. My thoughts on your above list would be to also consider

Impact Assessment

- Who will be impacted, and how

Processes and Functions

- What will we use Rock for? What existing processes will Rock support and how? What additional custom attributes will be required, by whom? How and when will they be maintained?

Does anyone in the community have any templates of any of these types of documents they would be willing to share?

Edit Answer

<p>Hi Derek.&nbsp; This is very valuable thinking.&nbsp; I'm working in a Government department at the moment on a software implementation project and see again the importance and value of having properly thought through transition plans.&nbsp; Most smaller churches, I'm guessing, don't have time or don't have the expertise to do this.&nbsp; If 'we' could put something together than was generic enough for others to use it would be very valuable, and appreciated.&nbsp; My thoughts on your above list would be to also consider</p>

<p>Impact Assessment</p>

<p>- Who will be impacted, and how</p>

<p>Processes and Functions</p>

<p>- What will we use Rock for?&nbsp; What existing processes will Rock support and how?&nbsp; What additional custom attributes will be required, by whom?&nbsp; How and when will they be maintained?</p>

<p>Does anyone in the community have any templates of any of these types of documents they would be willing to share?</p>

<p>Hi Derek.&nbsp; This is very valuable thinking.&nbsp; I'm working in a Government department at the moment on a software implementation project and see again the importance and value of having properly thought through transition plans.&nbsp; Most smaller churches, I'm guessing, don't have time or don't have the expertise to do this.&nbsp; If 'we' could put something together than was generic enough for others to use it would be very valuable, and appreciated.&nbsp; My thoughts on your above list would be to also consider</p>

<p>Impact Assessment</p>

<p>- Who will be impacted, and how</p>

<p>Processes and Functions</p>

<p>- What will we use Rock for?&nbsp; What existing processes will Rock support and how?&nbsp; What additional custom attributes will be required, by whom?&nbsp; How and when will they be maintained?</p>

<p>Does anyone in the community have any templates of any of these types of documents they would be willing to share?</p>

Save Cancel

Jon Edmiston · Answer 3 · 2015-06-27T12:49-07:00

0

Jon Edmiston replied 9 Years Ago

We at CCV are still pretty heads down on finishing the development for all the items we need. We'll soon though be transitioning into more training. As we do that we're trying to make as much of the training re-usable for others (as I hope other churches will do also). We did make this quick video to given our staff a quick overview of the scope of the transition. Probably not too reusable but perhaps it gives you some ideas.

https://sparkdevnetwork.wistia.com/medias/4zn30k3ysr

We'll share more as we get closer to 'D-Day'.

Edit Answer

<p>We at CCV are still pretty heads down on finishing the development for all the items we need. We'll soon though be transitioning into more training. As we do that we're trying to make as much of the training re-usable for others (as I hope other churches will do also). We did make this quick video to given our staff a quick overview of the scope of the transition. Probably not too reusable but perhaps it gives you some ideas.</p>

<p>https://sparkdevnetwork.wistia.com/medias/4zn30k3ysr</p>

<p>We'll share more as we get closer to 'D-Day'.</p>

<p>We at CCV are still pretty heads down on finishing the development for all the items we need. We'll soon though be transitioning into more training. As we do that we're trying to make as much of the training re-usable for others (as I hope other churches will do also). We did make this quick video to given our staff a quick overview of the scope of the transition. Probably not too reusable but perhaps it gives you some ideas.</p>

<p>https://sparkdevnetwork.wistia.com/medias/4zn30k3ysr</p>

<p>We'll share more as we get closer to 'D-Day'.</p>

Save Cancel

Elaine Lohroff · Answer 4 · 2023-02-21T09:16-07:00

0

Elaine Lohroff replied 1 Year Ago

I'd be interested to know if there are other churches' roll out plans here in the Q and A. Haven't found much yet. The OP here has a great start!

Question

1

Church Rock & Roll Out Plans

0

0

0

0