190 likes | 289 Views
This project aims to merge Catholic faith programs with technology, offering a interactive learning experience for all ages. The plan includes creating a fun catechism program, developing curriculum, and implementing a technology platform for educational and entertainment experiences. Critical success factors and a detailed project framework are outlined to ensure successful execution. Sub-committees with specific roles and responsibilities will be formed to achieve high-level milestones efficiently.
E N D
Faith & Technology Project Overview
Overview (What, How, When) • What? • What are we trying to accomplish • How? • How are we going to accomplish it • When? • When do we need to accomplish it by
What - Vision • Provide opportunities to use technology so all of our parish family (including preschool through adult) can learn about God and our Catholic faith through experience.
What - Target Audience: • Catechists (Educators) • Program Administrators • Pre K – Adult Education • Web Users • Wireless Device Users • Classrooms • Committee Members • Stakeholders • Content Authors
What –Project Goals • What is it we are trying to accomplish: • Merge Catholic faith based programs with technology. • Design a fun and intuitive catechism program. • Develop a catechism curriculum leveraging existing content and structure. • Implement technology platform to support rich educational and entertainment experience. • Implement technology supporting infrastructure. • Build instructional content using current media formats and technologies. • Multiple delivery platform support. • Develop a prototype by June. • Maintain, educate and support implemented solution. • Centralize management of users and content.
What – The Plan • Recommended Solution • Implement Solution Using Project Framework • Project Plan & Schedule • Plan Execution • Project Delivery • Solution Support • Training
How – Solution Overview • Major Decisions: • Defining the Content Solution • Programs / Courses / Content • Tools, Delivery Req., User Tracking, Scale factor, Content Linking, Mgmt • Process, approval, content asset creation, file support • Defining the Delivery Solution • Devices (TV, Browser, Wireless, Smartboards, Video – DVD, Print) • Classroom Target Group • Defining the Technology Solution (App – IT) • LMS, CMS, (.netvs .php), Web 2.0, User, Curriculum Mgmt. • Hosting (internal vs 3rd party) • Open Source vs 3rd Party • Discuss Project Framework • Method, Project Process, Phases • Review Project Plan • Time, Scope, Cost • Proof of Concept (Prototype) • Divide and Concur • Divide up into Groups (Strengths / Weakness, Skill Set) • Define & Document Requirements (who, what, when) • Individual tasks bubble up to complete Milestones • 1 Group for each of the 7 categories • Plan The Results • Next reporting period will need to present next steps for the 7 categories. • Link requirements to major milestones • Implement next steps in framework • Reporting and group communication
Proof of Concept (Prototype) • Define the following • Content • Target Audience • Content Delivery Vehicles • Content Production • Technology - Application • Technology – Infrastructure • Support • Training
How – Project Plan / Framework Units • Based on time • Left = 0 Days • Right = 140 Days Purpose Brainstorm Instructional Production Delivery Delivery Support Support Training Training Technology / Infrastructure
How – Sub Committees • Building the 7 Category Committees • Each category requires unique skill sets, divide accordingly • Volunteer for more than one, production is the largest piece • Each Group will need the following roles: • Lead – oversight and point of contact • Historian – document effort on wiki • Reporter – ask / answer questions for the committee team.
How – Work Breakdown Structure • Group Discussion • Assign Historian, Reporter for the week • Review the Project Plan for Sub-Committee • Review the Documents provided • Remember the What, How and When • Deliverables: • Requirements • Solutions • Time • Scope • Cost
When – High Level Milestones • Define the POC (Prototype) • Educate the Solution • Form Subcommittees • Define Requirements • High Level Project Schedule • Instructional Design • Technology – Authoring • Technology – Application • Technology – Delivery • Technology - Infrastructure • Production Plan • Prototype Scope • Delivery Plan • Delivery Communication • User Acceptance • Support Plan • Training Plan
Next Steps • Define the proof of concept • Educate the solution to the committee • Develop subcommittees • Introductions • Document resource skill sets • Determine • Historian • Reporter • Define • High level requirements • High level solution • Document • Open Questions • Issues • Work on base requirements for subcommittees • Collaborating
Open Thoughts • Collaboration – Wiki • Documenting Efforts – Wiki, Attachments • Section historians, document what, how and when • Section reporters list of any questions including section name, question • Discuss and document deliverables • Formulate a solution • Get prepared to discuss to committee