1. Review of project plan for Q3 and Q4

  • Prioritize following activities next week (please review):
    • developing reviewing templates:
      • Sample business case
      • Scope template
      • Stakeholders Analysis Tool done by quadrants
      • Business requirements
      • Functional Specifications (people need to understand the difference)
      • Project Kick-off Document
      • Communications template vs. Status Update (status could be subset of Communications template)
    • partnership opportunities
      • Facilities "PIT" Project Initiation Team
      • Lincoln Lab PMO
    • review and discussion of processes to incorporate into our project life cycle and task lists
      • QA
      • User Interface Design
      • Web Services
      • Accessibility/Usability

2. Scott Thorne of the Data Administration and Warehousing Team discusses best practices and benefits to accessing the DW resources on a project:

  • Resource requests
    • should be made during the planning phase (assigning team)
    • PM sends email to data-admin@mit.edu
  • Reporting requirements
    • owned by BA
    • should be completed during the requirements phase
    • can take 1-3 1 hour sessions, set up by the BA, facilitated by DM
    • member of DM will work with BA, business owner and key users (stakeholders) to capture reporting requirements
    • BA incorporates into documentation
    • should be completed prior to design
    • focus on what questions the report needs to answer as opposed to just identifying reports to be re-created
    • part of the gathering and documentation of business requirements
    • post information on the wiki to share
  • Business Process Model
    • owned by BA
    • included in the business requirements phase
    • part of the business requirements documentation
    • DM will help BA map the business processes, if desired (or BA can do on their own)
    • post on wiki to share
  • Conceptual modeling
    • owned by DM resource
    • should begin before or during requirements phase
    • can take up to 1-3 2 hour sessions, set up by the BA, facilitated by DM
    • member of DM will work with BA, business owner and key users (identified by business) to create conceptual model (document the relationships)
    • member of DM team will create the conceptual data model
    • meetings with business owners and BA for information gathering and review are coordinated through the PM
    • BA incorporates into documentation
    • should be completed prior to final requirements sign off
      • test requirements against conceptual model and business process maps as further validation
      • modify as needed
    • team can then take conceptual model to physical level (design) and define data (fields)
    • team can then test design against conceptual model prior to design review
    • post to wiki to share
  • Maintenance requests
    • enhancement requests should always refer to model to see if:
      • you will break model with additional functionality OR
      • you need to extend the model to incorporate new functionality
  • More information: Conceptual Data Model Overview
  • No labels