Welcome to Bible.org Project tracking and ticket system

Table of Contents

  1. Project proposal for creating a Request for approval for a project/task
  2. Actions:
  3. Starting Points
this page is a general template for the requirements approval process and the subsequent project tracking of deliverables as specified in the requirements section of this doc or the to see a finished sample of this requirements google doc see Hulls Blog requirement the format is used here as a sample

Section 1

Describe the requirements with an emphsis on deliverable features and the hand off to ops & LCS

Project proposal for creating a Request for approval for a project/task

Project Name: Hull’s Blog Setup Date: 8/31/2007 Revision 1 9/4/2007 added requirements from LCS rep and mods from Chris Goodman Revision 2 9/5/2007 project approved added approval signatures and actions assigned below Task #: 40.1 TRAC Project: Blogs Project Author: mguthrie

  • Project description: Install new Drupal installation and configure using BORG policies for setting up new blog. Basically mirror the functionality of Bock’s blog with separate themes for each user and add the ability to add up to 50 people by a person who can be trained who outside the primary developer
  • Point of contact Chris Goodman, Mitch Guthrie
  • Background, Need and Projected Benefit:
    • Background: Hull would like to be able to blog. Bible.org will host site on http://blog.bible.org/hull and user can control content.
    • Need: Upgrade to Drupal 5.2, correct WYSIWYG modules and add image capability. Also, disable creation of new user accounts and allow anonymous commenting with captcha for spam protection.
    • Benefit: Extend bible.org’s multi-modal engagement offerings enabling users to connect with authors/messages through multiple modes. We can further partner with Bill Hull and allow him a platform for discussion that will bring attention to both Hull’s ministry and bible.org.
    • Approach: Install, customize, theme as the first user of the bible.org blogging site for invited users e.g. site staff/authors, moderators, The approach of this more general implementation will be to allow certain members to be highlighted or showcased among the other population. The Hull user will be one of these.

# The initial user population estimate will be under 50 with Hull being the 1st and critical staff being a later phase. # A quick review of several sites will be done for example http://www.theresurgence.com/ , http://www.sabdaspace.com/ , http://www.sabdaspace.com/blogger , http://www.sabdaspace.com/blog/john_adisubrata and working with the customer rep a feature/look and feel baseline established for the initial delivery on this task

  • List of critical feature and deliverables that will determine the development time (include any training material for users and LCS:
    • Install Drupal 5.2
    • Install 3rd party modules
    • TinyMCE for wysiwyg
    • Image, and img_assist
    • Add modules for Captcha
    • Add the ability to easily implement ads (pulling from OpenAds? )
    • Module to support automatic blog category/topic list – (see http://www.jesuscreed.org/ - right side for example)
    • Create user documentation
    • Create documentation for a person other than Mitch to add new blog users
    • Separate themes and customization by user
    • Customize theme for Hull
      • Re-design of amadou theme from drupal.org
      • Let Chris develop header and color scheme
    • Needs the ability for users to adjust/customize blocks (e.g. blog roll etc.)
    • Re-configure site for security
      • Configured roles for blogger and administrator
      • Disable account creation. Allow anonymous moderated commenting using captchas for spam prevention.
  • Estimate of the resources required to begin phase 1 and the time to complete:
    • Resources needed 1,N
      • Time – Mitch Guthrie
      • Test Environment
        • Will use mark.bible.org for final project
      • Testers for testing
        • Bill Hull, Chris Goodman, Marc Buffet, Dave Austin
  • Develop a Risk statement with respect to delivering on time and schedule. The risk on this project is minimal and involves the extent that Drupal can hanled the flexibility that is described in theming etc
  • Estimated time to complete or need date: The process of adding the blog and customizing it should take24 hours of Mitch’s time .
    • Indicate any meaningful or natural development phases of the project.
      • Phase 1: Install
      • Phase 2: Add new modules (captcha)
      • Phase 3: Allow test users to trial
      • Phase 4: Make adjustments sent by testers
      • Phase 5 perform an Operational Test (OT&E) which demonstrates
        • The roles of user and the first level user support person (named by the LCS manager),
        • A person other than the development manager (named by the LCS manager), trained to set up new blogs so that Mitch isn't the only one who knows how to do this be part of this project?
      • Phase 6: Official rollout, passing off to LCS.
  • Key Individuals to work on the project plan and the development
    • Project Manager and coordinator: Mitch Guthrie
    • Development manager: Mitch Guthrie
    • Customer representative: Chris Goodman
    • Life Cycle Support (LCS) representative: Hampton Keathley
    • Project approval Authority: David Austin
    • The name of any volunteers that are interested in working on the project and any sponsors or funding that has already been identified as available to the project
    • Not applicable

Requirement Approvals

  1. Customer representative email from Chris Goodman date 9/5/2007_
  2. Life Cycle Support (LCS) Rep. email from Hampton Keathley date 9/5/2007
  3. Project approval Authority David Austin date 9/5/2007

Actions:

  • Mitch you are authorizes to begin work on this task and to charge the task. The budget is 24 hrs.
  • Add this to the TRAC project titled Blog make this release 2 with bocks blog as release 1
  • Add on your TRAC deliverables those identified above
  • Add in the TRAC timeline the DT&E testing and OT&E testing and the turn over to LCS (project complete)

Section 2

describe what is in the various Releases, timelines and components as needed

Section 3

describe what you want your testers to do and any other instructions you want to transmit to the reviewers

this development project trac will close when the project is finished and the Development team disbanded upon completion of the deliverables and signoff of the operations and life cycle support personal any trouble tickets on the operational system will be started on a new instance of Trac any questions call daustin

Starting Points

last updated 21sept07 da