echurchgive: stakeholder survey and analysis

8/13/2019 eChurchGive: Stakeholder Survey and Analysis

1/10

eChurchGive: Stakeholder Survey and Analysis

This document will contain action items for stakeholders (Who is a stakeholder and why doesthe development team need information from them?) to complete. This list of priorities will be

used to keep track of all of the things the stakeholders need to do in order for the development

team to maintain steady progress. These priorities are a work-in-progress, please check back

frequently for changes and updates (at least once a day).

There will be some additional information provided in this document to provide context for the

questions being asked and the action items being requested. If you do not understand

something, comment on the word or phrase and a developer will be glad to teach you. Learning

should never stop. Plus we love to share our knowledge!

You may make comments regarding new priorities to be added and a developer will add it.

Note: Instead of editing this page directly, please use comments. To comment on the whole

document, click on the Comments button near the top right of the screen. You can add a

comment to a particular part of the document by selecting a section of text, then going to the

Insert menu at the top of the page and choosing Comment. A little box will appear on the side of

the screen and the commented text will become highlighted. Commented text looks like this. You

can also see all comments (including resolved ones) by clicking on the Comments button at the

top right of the page.

Googles explanation of comments is here, and their tutorial for all of Google Docs is here.
https://support.google.com/docs/bin/answer.py?hl=en&answer=143298&topic=21014&ctx=topichttps://support.google.com/docs/bin/answer.py?hl=en&answer=143206http://www.google.com/url?q=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FStakeholder_analysis&sa=D&sntz=1&usg=AFQjCNHYkNGVzmzRiiPpVsqjWM4jtdX0jAhttps://support.google.com/docs/bin/answer.py?hl=en&answer=143206https://support.google.com/docs/bin/answer.py?hl=en&answer=143298&topic=21014&ctx=topichttp://www.google.com/url?q=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FStakeholder_analysis&sa=D&sntz=1&usg=AFQjCNHYkNGVzmzRiiPpVsqjWM4jtdX0jAhttp://www.google.com/url?q=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FStakeholder_analysis&sa=D&sntz=1&usg=AFQjCNHYkNGVzmzRiiPpVsqjWM4jtdX0jA


2/10

Product Features

Here we will discuss the details around what it will take to implement the features of our

applications.

Live Streaming

This list will be used to plan and design how we are going to implement the end to end process

of our live streaming service. Please note that most of the work will be on the network churchs

administrations side. This is where the video will be uploaded to FatFractal (i.e. the cloud). That

side of things is quite complicated it will take weeks for research, planning, development, and

testing. The church-goer end, on the other hand, will be complete soon.

Context: Here is the list of components in order from start to end:

The church service being aired. This church will be at a church that is a

client/paying-customer of eChurchGive(i.e. network church as O'Neil prefers).

Recording equipment to capture the service.

Live video camera(s)

There are many types of cameras that a church may have or need.

Each of these may have different types of digital or analog outputs for the

signal(s) we will need to cater to all of these possibilities or tell them what

cables they need to convert to in order for us to have the proper signal.These signal(s) could be just video or could have audio combined with

them.

Live audio recording equipment

This will be no single mic they may have dozens of mics used to record

their vocalists, band members, pastors, special guests, and sometimes

audience members.

All of the signals from the mics will be coming into a single sound board or

mixer. These mixers usually come with two or RCA auxiliary analog

outputs but there are many different possibilities here.

Most venues should have all of this we will need to cater to all of thesepossibilities or tell them what cables they need to convert to in order for us

to have the proper signal.

Equipment to store the service digitally

An audio interface (a signal converter/merger)

It will be between the analog or digital audio and video output signals and

the digital inputs of a computer.


3/10

It will have to have an output that is appropriate for the size of the signal it

is carrying and that can run directly into an input on the computer

described below.

Note that if the church is responsible for capturing their own audio and

video we must be prepared to provide an array of different interfaces for

turning their signals into the digital signals that we need. A computer

We need a computer of a very specific design. eChurchGive should

probably provide this.

This computer will use the interface above to turn the signal into a digital

stream at the bit rate that we need. The input for the computer must

match with the output for the interface above.

Equipment to upload the live stream to FatFractal

The same computer listed above will be used for this.

Video processing and distribution software

This software will need to be able translate the incoming signalfrom the audio interface and send it to FatFractal.

To upload the stream to FatFractal it must adhere to the HTTP

method for sending video across the Internet.

A fast broadband internet connection. Something around 10 Mbps upload

speed.

A service to distribute the stream to millions of users

FatFractal! FatFractal only needs a few modifications to handle this. It will be a

few days worth of work for their team. They may not have time for this until after

the next release of FatFractal at the end of June.

Client side software to download the stream and display the live stream of the service

Questions for the stakeholders regarding the live video streaming service:

1. Review and understand the above list. If you do not understand something please

comment on the item and we will be glad to help out.

2. What is the average upload speed that churches are going to have?

3. Should a minimum upload speed be required? What should it be?

4. Who will be responsible for what part of the process (network church vs. eChurchGive)?

a. Is eChurchGive going to provide recording equipment (for video or audio) for all or

some of the network churches?

i. Will it even be an option for them?

b. Who will provide the audio interface?

i. Which audio interface should be used?

ii. What is the budget?

c. Which computers are going to be purchased to capture and serve the stream to

FatFractal?

i. What is the budget?

d. What software is going to be used to capture and serve the stream to FatFractal?


4/10

i. How to acquire the software:

1. purchase it?

2. build it?

3. find a free open source solution that is already created?

5. How are churches currently handling video and audio recording if they have it?

a. We need a few different cases to fully understand the process and protocol.b. A churchs video and audio techs are going to be users of our software. We need

a user requirement analysis of them.

6. How are churches currently handling streaming if they have it already?

a. What models and processes are our competitors using?

i. What software are they using?

ii. What hardware are they using?

7. How should the developers test what they build?

a. Could testing be done at a church such as Berean?

i. Is this ok to have the developers drive all the way to Berean for testing?

b. Should equipment be provided to the developers for testing?c. Could the non-developers on the team handle the testing process?

8. How does a church schedule their live streaming events?

a. How should we handle this? e.g. What information do we need to collect from the

churches for each event?

Donation Processing

1. Are there going to be any restrictions on the donation amounts, i.e. is there a

maximum/minimum amount, are decimal numbers allowed?

2. When setting up a churchs merchant account, will they have to go through the

eChurchGive staff to set up an IPPay account? Will they be able to do this on their own?

3. Before donations can go live, we need a terminal ID for each churchs merchant account,

i.e. their IPPay account ID, so to add this functionality well need to know if a church

administrator will be able to log in and enter a terminal ID themselves, or if only an

eChurchGive admin would have this privilege.

4. We also need the eChurchGive merchant account information, because we will have any

donations to a church that does not have its own merchant account be directed to the

eChurchGive merchant account by default.


5/10

User Interface Design

1. An updated storyboard that includes the features mentioned in the Development

Priorities document.

2. Access to all of the graphical assets from the finished storyboard.

3. The development team needs to know how to title/name every button, link, and page that

is part of the app.

a. Consider changing all of the names of pages that contain My in them to

something less cliche. We need short and simple names for our pages. What is

a cliche?
http://www.google.com/url?q=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FClich%25C3%25A9&sa=D&sntz=1&usg=AFQjCNEtNvO2cot14UhzGD3hVTkClAaOdwhttp://www.google.com/url?q=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FClich%25C3%25A9&sa=D&sntz=1&usg=AFQjCNEtNvO2cot14UhzGD3hVTkClAaOdwhttps://docs.google.com/document/pub?id=1WY8GL1cDMf7eUKsP7kzRgb6biSuQNwg-kUS49C7FpqUhttps://docs.google.com/document/pub?id=1WY8GL1cDMf7eUKsP7kzRgb6biSuQNwg-kUS49C7FpqU


6/10

User Requirements and Analysis

These items will assist in clarifying the design of the user interface to the team. What is a user

requirement analysis?

General

1. A detailed step-by-step description of exactly what process our sales team is planning on

going through when demoing Version 1 of eChurchGive: GivingOnTheGo to potential

investors or eChurchGive clients.

a. Include the exact date of the conference that this app will be demoed.

b. Describe the background and experience of the investors or potential

eChurchGive clients.

Testing

1. Make sure to check for updates to the Critique... documents to be sure the development

team is designing and implementing the final product the way you desire. This is very

important. Be clear and blunt with your opinions you cant hurt an engineers feelings,

promise. Do everything you can possibly think of to our apps. Try and blow them

up doing things that do not even make sense.The two documents are shared with

you and titled:a. Critique of the iPhone App (Round X)

b. Critique of the Mobile Web App

2. Make sure you test the applications on as many devices as you can.

a. For the mobile web application, when you are mentioning a problem, list the

browser you are using and the make and model of your handset.

3. To test the iPhone app follow these instructions: Read Me to test the iPhone App.
https://docs.google.com/document/pub?id=1_XR1T-ihsynuszg5MTfzGq3nth-uU_I5GCPtz4bnq-ohttps://docs.google.com/document/pub?id=1_XR1T-ihsynuszg5MTfzGq3nth-uU_I5GCPtz4bnq-ohttp://www.google.com/url?q=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FRequirements_analysis&sa=D&sntz=1&usg=AFQjCNHRwFrCXsfeMNwtEuIISrXPr4CcMAhttp://www.google.com/url?q=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FRequirements_analysis&sa=D&sntz=1&usg=AFQjCNHRwFrCXsfeMNwtEuIISrXPr4CcMA


7/10

Business Modeling

General

1. Are the donation and live streaming services going to be separate products for the

network churches to purchase?

Marketing

1. Discuss the issuing of any marketing materials that are produced with the developers.

This will make sure you are making promises to your customers and investors that we

can reasonably meet.2. A one sentence description of the main mission or purpose of eChurchGives

GivingOnTheGo. This will be used on the homepage of the web app.

3. A one paragraph description of the main mission or purpose of eChurchGives

GivingOnTheGo. This will used on an About page of the web app.

4. A quick and dirty competitor analysis. This will make sure we are clear as to what

features are the most valuable and unique. With this information we can take advantage

of others faults and know who may be better than us at other things.
http://www.google.com/url?q=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FCompetitor_analysis&sa=D&sntz=1&usg=AFQjCNFhaNFRJ-8yAiR3Ez6yvJD8rhijNQ


8/10

Communication

These items will ensure that we are all communicating regularly and accurately. It is of utmost

importance for the interactions between all team members to be completely clear. This list

should help us all improve our communication procedures.

1. To contact any of the developers, refer here: eChurchGive Team Contact List

2. A list of all of the people that we should share Google docs with and their preferred

emails that they will use to access each Google doc.

3. A list of all of the people that we should correspond with via email and their preferred

email addresses for email correspondence.

4. A list that describes what eChurchGive team member is responsible for what type of

question or discussion (e.g. O'Neil: Financial Transactions, Ana: Business Modeling and

Marketing, Kevin: FatFractal Issues etc.)

5. Consider using Google Docs and DropBox instead of Smartsheet.

6. Sign up for Google Docs: https://docs.google.com/

7. Sign up for DropBox: 'https://www.dropbox.com/'

8. Sign up for Skype: http://skype.com/intl/en-us/home
http://www.google.com/url?q=http%3A%2F%2Fskype.com%2Fintl%2Fen-us%2Fhome&sa=D&sntz=1&usg=AFQjCNEAyzlOytFHysBxKb7uRX98iintNwhttp://www.google.com/url?q=http%3A%2F%2Fdb.tt%2FoVZJQNk&sa=D&sntz=1&usg=AFQjCNEjQo690rbw7BLETGG9mEDzYCLgkghttps://drive.google.com/https://docs.google.com/spreadsheet/pub?key=0AiG7Bp-4ayOWdG1mT1hBTXZDWWRFUm5DUzV2dkdqOHc&output=html


9/10

Team Enlightenment

These items will help us understand more about: the product that we are designing/developing

and the tools that we are using for online collaboration.

1. Read and fully understand Apples App Store Review Guidelines.

a. Comment on any issues you notice with our plan.

2. Learn all of the relevant features of Google Docs that you can use:

https://support.google.com/docs/

3. Learn DropBoxs full capabilities: https://www.dropbox.com/

4. Learn Skypes full capabilities: http://skype.com/intl/en-us/home
http://www.google.com/url?q=http%3A%2F%2Fskype.com%2Fintl%2Fen-us%2Fhome&sa=D&sntz=1&usg=AFQjCNEAyzlOytFHysBxKb7uRX98iintNwhttps://www.google.com/url?q=https%3A%2F%2Fwww.dropbox.com%2F&sa=D&sntz=1&usg=AFQjCNEPyYmnWXCaUnWKkLMHYdjoq_jreQhttps://support.google.com/docs/https://docs.google.com/document/pub?id=1b2QI5ipHbeb5u9a4mFmM12wS-NPIxdu84UTW0P6ZHgc


10/10

Team Management

These items will correspond to things such as team building, team training, and team

preparation.

Regarding Current Developers

The entire development team has not officially discussed or confirmed an extension of

our contract past 6/8/2012. The entire team has announced interest in working with

eChurchGive further. To make this official we will have to discuss exactly what

deliverables the development team will be responsible for by what date. The developers

all have other opportunities at hand and need to know how long they will be working for.

Will the entire team be contracted on for more time?

Are we still going to be on as contractors or are we going to be official developers

on the team?

How much longer can we expect to have work with eChurchGive?

Should we expect a specific set of deliverables that we need to work on? What

will they be?

Future Team Members

1. Contact details for the iPhone developer that Ana would like us to bring on to the

development team.

echurchgive: stakeholder survey and analysis

Documents