YSA Project meeting notes - Q1 2010

YSA Project Index edit
Home Getting Started Our Team Meetings	Requirements Use Cases Features Mockups Architecture Social Media
Sitemap	Get Connected Be Inspired Stay Strong

27 April 2010

• We had David Wariner and Steve Hansen on the call.
• We didn't really get into the wireframes that Erika put together, though Stephan did mention that he posted them on the wiki.
• David is going to work on integrating the Google Maps to the site.

20 April 2010

Stephan ran the meeting

1. He gave an overview of what happened at the YSA Council meeting. There was a long list of ideas that might be useful on the site.
2. We talked about dividing up the JIRA Tasks
   • Components in JIRA: based on function and/or section of the website
   • There are alot of fine-grained tasks right now - don't be afraid to attack them, as most are fairly small.
   • The tasks are based on the Hallmark features
3. The Community wants wireframes, sitemaps, or something similar to help organize the website before coding occurs.
   • Erica will put together some wireframes for the delegation workflow.
     • What is the process that a 70 will need to do to delegate?
     • What is the process that a YSA delegate needs to do?
   • The specs haven't been created because they are all in Nic's brain.
   • Joseph will go over the event creation process
4. Going forward, the site will be heavily templated. There is a standard church website template that all sites are going to use. That means there's less design work for us.
5. All of the Hallmark features have to be done by a week from Friday (April 30th).
   • The payment stuff has been postponed - it's waiting on some internal payment services.
   • CDOL = Church Directory of Leaders - let the leaders create events.
     • Only the area presidency, and delegated YSAs can create events
   • maps: a data sharing agreement is in the works
6. SMS service is setup now.
   • Once we request access, we can start using that.

12 April 2010

1. be inspired content
   • 12 apostles/ first presidency
   • question & answer
   • area presidency could also add specific things
2. How we should communicate to each other
   • wiki should list decisions
   • jira issue tracking, work items
   • email distribution - ongoing conversation

Meeting notes from Cassie McDaniel

File:YSA 3-12-2010.pdf

The Following Topics Were Discussed

1. Introductions
2. Identify who will drive the project, PM
   • Rob Fotheringham will work with the persons who identify themselves as able to do PM work
3. YSA Project Vision (from Nic)
   • There is a need (a gap) in the Church's ability to retain youth between 18 and marriage if the youth doesn't go on a mission or go to a Church school
   • Nic has been involved and present with the governing council, who has said that the youth need to be connected to Christ, each other, and good causes
   • The portions of the site are as follows
     1. Get Connected allows YSA to connect to each other using Facebook.
     2. Be Inspired (content driven from headquarters and from area managers). This portion may be limited to the 12 Apostles and the First Presidency and will come from a YSA process in a video Q/A format. Videos will be in the Mormon Channel format. Then youth could attach to the video content that has been inspirational to them (and attached to their profile via the tags). This achieves a connection to prophetic word and to each other. A crowdsourcing tool has already been created for LDS.org nextgen
     3. Stay Strong. Resources for help surviving and thriving during that tough time between 18 and marriage
4. Decisions and major points should be documented on the wiki, JIRA will hold tasks, and conversation and take place in the google email group. LDSTech protected forums are an option for group project discussion available.
   • Jacob Floyd has mentioned that he'd take the task to keep the wiki up to date

For Friday's Meeting with the Governing Council

Need something that's a little more built-out before finding the testing group

• This meeting will be a status meeting, as much as possible, from now on
• General look and feel of the new theme(face lift with new images and possibly fonts)if possible

Weekly Meeting

• This meeting will be held at 3:30 on Tuesdays going forward