Docstoc

Clinical Informatics and Data Management Unit - Monash University

Document Sample
Clinical Informatics and Data Management Unit - Monash University Powered By Docstoc
					  CLINICAL INFORMATICS AND DATA MANAGEMENT UNIT
DEPARTMENT OF EPIDEMIOLOGY AND PREVENTIVE MEDICINE
                MONASH UNIVERSITY




{ENTER PROJECT
     NAME}


                 PROJECT BRIEF
1.        DOCUMENT INFORMATION

 Project Name:
 Prepared By:                                                          Document Version No:
 Title:                                                                Document Version Date:
 Reviewed By:                                                          Review Date:




1.1        STAKEHOLDERS
           This project has the following stakeholders
Name                      Title                      Organization   Phone/Extension   Contact
                          Principal Investigator

                          Study Project Manager

Christopher Reid          Head, CIDMU                CIDMU          x30752            Christopher.Reid@monash.edu

David Morrison            Systems Development Mgr    CIDMU          x30242            David.Morrison@monash.edu




CIDMU_Project Brief TemplateV5                      Page 1 of 9                                 11/29/2012 6:46
2.         TABLE OF CONTENTS


1.      DOCUMENT INFORMATION ....................................................................................................................1

     1.1      STAKEHOLDERS ..............................................................................................................................................1

2.      TABLE OF CONTENTS ..............................................................................................................................2

3.      PROJECT DEFINITION ..............................................................................................................................3

     3.1      BACKGROUND ...............................................................................................................................................3
     3.2      PROJECT OBJECTIVES ......................................................................................................................................3
     3.3      BENEFITS......................................................................................................................................................4
     3.4      INTERESTED PARTIES.......................................................................................................................................4
     3.5      RISK ............................................................................................................................................................4
     3.6      CONSTRAINTS ...............................................................................................................................................4
     3.7      INTEGRATION ................................................................................................................................................4
     3.8      MIGRATION ...................................................................................................................................................4

4.      PROJECT MANAGEMENT TEAM STRUCTURE ...........................................................................................4

     4.1 ROLE DESCRIPTIONS .......................................................................................................................................5
     EXECUTIVE..............................................................................................................................................................5
     SENIOR SUPPLIER .....................................................................................................................................................5
     STUDY PROJECT MANAGER ........................................................................................................................................5
     BUSINESS ANALYST ..................................................................................................................................................5
     SCRUMMASTER .......................................................................................................................................................5
     CHAMPION USER ......................................................................................................................................................5
     4.2 ROLES AND RESPONSIBILITIES ...........................................................................................................................6

5.      REFERENCES ...........................................................................................................................................6




CIDMU_Project Brief TemplateV5                                                  Page 2 of 9                                                              11/29/2012 6:46
3.     PROJECT DEFINITION
3.1      BACKGROUND
        CLIENT to COMPLETE - (Please provide a short description of the project)




3.2      PROJECT OBJECTIVES
        CLIENT TO COMPLETE – What do you want the system to do?
        EG: To develop a web based data capture and reporting systems that enables:
         a) Collection of data from XXX sites?


         b) Collection of data for XXX participants?


         c) Collection of data for XX visits per participant?


         d) Collection of data for XXX duration?


         e) Collection of data on XX forms (e.g. baseline, follow up adverse event). Are any of the
            forms repetitive (e.g. daily)?


         f)   Is the proposed database an entirely new system or is it a web version of an existing
              system?


         g) If an existing system is available, how different is the proposed system from the existing
            system?


         h) Do we need to import data from an existing system? If yes, should this be done
            periodically or once for all?


         i)   How much data do you intend to collect using the proposed database (number of records
              and number of data elements)?




         j)   Does the study require web randomisation?




         k) Are there any reporting requirements? E.g. management reports and clinical reports


CIDMU_Project Brief TemplateV5                  Page 3 of 9                              11/29/2012 6:46
         l)     Any other special requirements?



3.3      BENEFITS
              CLIENT TO COMPLETE – What are the benefits you are expecting from this system – data
              capture, reporting etc.?
              EG: The following benefits are expected from implementation of the system:
              Data capture from multiple sites
              On-line error checking
              Centralised reporting




3.4      INTERESTED PARTIES
   CLIENT TO COMPLETE – Who else is involved in this project that may want to have a say – other
   stakeholders?




3.5      RISK
   CLIENT TO COMPLETE - (Identify risks associated with development, delay, stakeholders etc.)




3.6      CONSTRAINTS
   CLIENT TO COMPLETE - Are there any constraints to the project that we need to be aware of?
   e.g. Proposed project time lines i.e. when do you want the system to be available by? Budget i.e.
   is funding to be provided by a grant application, the outcome of which is as yet, unknown?




3.7      INTEGRATION
   CLIENT TO COMPLETE - Are there any data feeds or interfaces with other systems to be
   developed?




3.8     MIGRATION

   CLIENT TO COMPLETE – Does any existing data require to be migrated to the new system? If
   so, is a sample extract available, database schema and/or data dictionary?




CIDMU_Project Brief TemplateV5                    Page 4 of 9                              11/29/2012 6:46
3.9     AVAILABILITY
   CLIENT TO COMPLETE – When is the service expected to be available? Business Hours,
   Weekends?




3.10    CAPACITY
   CLIENT TO COMPLETE – How many users are expected to connect? How many would connect
   at a time?




3.11    SUPPORT
   CLIENT TO COMPLETE – What after development support is required?




3.12    BUDGET
   CLIENT TO COMPLETE – Have you secured a grant? What budget have you allocated for data
   management?




CIDMU_Project Brief TemplateV5           Page 5 of 9                         11/29/2012 6:46
CIDMU_Project Brief TemplateV5   Page 6 of 9   11/29/2012 6:46
5.     PROJECT MANAGEMENT TEAM STRUCTURE


     CLIENT to COMPLETE - Please nominate as identified in chart

5.1      ROLE DESCRIPTIONS

                                              Executive:
                                        Chris Reid (CIDMU) +
                                        Principle Investigator


                             Senior Supplier:            Study Project
                             David Morrison                Manager:
                                (CIDMU)                (CLIENT Nominee)



                             Business Analyst:          Champion User:
                            (CIDMU Nominee)            (CLIENT Nominee)




                          Project ScrumMaster:
                            (CIDMU Nominee)



EXECUTIVE
         (CLIENT TO COMPLETE - Name the key stakeholders that will sign off on the requirements
         and approval budget expenditure)


SENIOR SUPPLIER
         (This will be the CIDMU Systems Development Manager)


STUDY PROJECT MANAGER
         (CLIENT to complete - This will be the Study Project Manager that will be heavily involved in
         the requirements specifications, application development and user testing)


BUSINESS ANALYST
         (This will be the business analyst for the project from CIDMU)


SCRUMMASTER
         (This will be the software development team leader for the project from CIDMU)




CIDMU_Project Brief TemplateV5                     Page 7 of 9                            11/29/2012 6:46
CHAMPION USER

         (CLIENT to complete - This will be the main user of the system, that may be heavily involved
         in the requirements specifications, application development and user testing)



5.2      ROLES AND RESPONSIBILITIES


                        Approve the Project including budget
                        Approve the System Requirements Specification
       Executive
                        Confirm acceptance of the projects product
                        Provide executive support to the project team
                        Verify the System Requirements Specification
                        Provide resources to undertake project activities
     Senior Supplier
                        Provide technical expertise and assistance
                        Oversee project progress
                        Participate in all sprint planning and review meetings
                        Prepare the System Requirements Specification with Business Analyst
      Study Project
                        Manage the priorities of the project
        Manager
                        Collate system improvements and change requests
                        Provide acceptance of the project product
                        Participate in all workshops, sprint planning and review meetings
                        Prepare the System Requirements Specification
 Business Analyst       Manage the Initiation phase of project
                        Collate system requirements and User Acceptance Tests
                        Provide systems design documentation
                        Participate in all sprint planning and review meetings
                        Assist with the System Requirements Specification with Business Analyst
      ScrumMaster
                        Manage the priorities of the software development team
                        Manage the Scrum development process
                        Provide project progress reporting
                        Assist with the User Acceptance Test
     Champion User      Assist with product Usability Test
                        Provide acceptance of the project product



6.      REFERENCES
        CLIENT TO SUPPLY
                                        Data Dictionary
                                        Project Protocol
                                        Any other relevant documentation




CIDMU_Project Brief TemplateV5                       Page 8 of 9                                  11/29/2012 6:46

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:0
posted:1/3/2014
language:Unknown
pages:9