Scribd Logo
Upload

Welcome to Scribd!

  • 67 views

    Sample Project Plan

    Uploaded by

    chamzowxexy
    The document outlines a work breakdown structure for a project with tasks such as database, application, and report design having durations of 3 to 25 days and status of open; it also describes a risk of inexperience with Microsoft Access potentially slowing development and increasing times by 46% which can be addressed through training and bringing in experts.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd

    Sample Project Plan

    Uploaded by

    chamzowxexy
    67 views5 pages
    The document outlines a work breakdown structure for a project with tasks such as database, application, and report design having durations of 3 to 25 days and status of open; it also describes a risk of inexperience with Microsoft Access potentially slowing development and increasing times by 46% which can be addressed through training and bringing in experts.

    Original Description:

    It is really helpful. :)

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document outlines a work breakdown structure for a project with tasks such as database, application, and report design having durations of 3 to 25 days and status of open; it also describes a risk of inexperience with Microsoft Access potentially slowing development and increasing times by 46% which can be addressed through training and bringing in experts.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    67 views5 pages

    Sample Project Plan

    Uploaded by

    chamzowxexy
    The document outlines a work breakdown structure for a project with tasks such as database, application, and report design having durations of 3 to 25 days and status of open; it also describes a risk of inexperience with Microsoft Access potentially slowing development and increasing times by 46% which can be addressed through training and bringing in experts.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 5
    At a glance
    Powered by AI
    The document discusses a project work breakdown structure, risk assessment, and requirements for a project.

    The risk identified is that the project team members have not programmed in Microsoft Access before, which may slow down development.

    Functional and non-functional requirements are described. Functional requirements are process-oriented and information-oriented. Non-functional requirements are operational, performance, security, cultural/political.

    Work Breakdown Structure

    Task ID 1 1.1 1.1.1 1.1.2 1.2 Task Name Design Phase Development database design document Staging database design Suspense database design Development rejects-handling design document Duration (days) Discrepancy 25 10 10 10 8 1.1.1, 1.1.2 Status Open Open Open Open

    Open Open

    1.2.1 1.3 1.3.1 1.4 1.4.1 1.5 1.5.1

    Rejects-handling engine design Develop OLAP design document Universe design Develop OLAP design part 1 High-priority reports design Develop application design Group consolidation and corporate reporting (GCCR) maintenance application design

    9 9 7 7 8 8 9
    1.1.1, 1.1.2

    Open Open Open Open Open Open

    1.6 1.6.1 1.7 1.7.1 1.7.2 1.7.3 1.8 1.8.1 1.8.1.1 1.8.1.2 1.8.1.3

    Exact, transform, load (ETL) design document Data export utility design Application design document Web entry application UI design Web entry application UI design sign-off Web entry forms and database model validation Functional requirements document Application Design User Authentication Call logging Search

    3 3 20 20 2 12 10 10 5 3 4

    Open Open Open Open Open Open Open Open Open Open Open

    RISK ASSESSMENT

    Risk #1:

    The development of this system likely will be slowed considerably because project team members have not programmed in Microsoft Access prior to this project. Medium probability of risk This risk likely will increase the time to complete programming tasks by 46%.

    Likelihood of risk: Potential Impact on the project:

    Ways to address this risk: It is very important that time and resources are allocated to up-front training in Microsoft Access for the programmers who are used for this project. Adequate training will reduce the initial learning curve for Microsoft access when programming begins. Additionally, outside Microsoft Access expertise should be brought in for at least some part of the early programming tasks. This person should be used to provide experiential knowledge to the project team so that Microsoft Access related issues (of which Microsoft access programmers would be unaware) are overcome.

    Functional Requirement Functional Requirement Processoriented Description A process the system must perform; a process the system must do Example Informationoriented Information the system must contain. The system must allow registered customers to review their own order history for the past three years. The system must check incoming customer orders for inventory availability. The system should allow student to view a course schedule while registering for classes. The system must retain customer order history for three years. The system must include real-time inventory levels at all warehouses. The system must include budgeted and actual sales and expense amounts for current year and three previous years.

    Nonfunctional Requirement Nonfunctional Requirement Operational Description The physical and technical environments in which the system will operate Examples Perform The speedy capacity, and reliability of the system Security Who has authorized access to the system under what circumstances Cultural and political factors and legal requirements that affect the system The system can run on handheld devices. The system should be able to integrate with the existing inventory system. The system should be able to work on any Web browser. Any interaction between the user and the system should not exceed 2 seconds. The system should be available for use 24 hours per day, 365 days per day. Only direct managers can see personal records staff. The system includes all available safeguards from viruses, worms, Trojan horses, etc. The system should be able to distinguish between Japan currency and currency from other nations. Personal information is protected in compliance with the Data Protection Act.

    Cultural and Political

    Project Standards
    Types of Standards Examples Documentation Standards The date project name should appear as a header on all documentation. All deliverables should be added to the project binder and recorded in its table of contents. Coding Standards All modules of code should include a header that lists the programmer, last date of update, and a short description of the purpose of the code. Indentions should be used to indicate loops, if-then-else statements, and case statements. On average, every program should include one line of comments for every five line code. Procedural Standards Record actual task progress in the work plan every Monday 8:00 A.M. Report to project update meeting on Fridays at 5:00 A.M. All changes to a requirements document must be approved by the project manager. Specification requirement standards Name of the program to be created Description of the programs purpose Special calculations that need to be calculated Business rules that must be incorporated into the program Due date User interface design standards Labels will appear in boldface text, left-justified, and followed by a colon The tab order of the screen will move from the top left of the bottom right. Accelerators keys will be provided for all updatable fields.

    Reporting Structure

    Project Manager (Michael)

    Functional Lead (Fatima)

    Technical Lead (Avvy)

    Analyst (Engressa)

    Programmer (Ash)

    Analyst

    (Jane)

    Programmer (Misty)

    Analyst (Raymund)

    You might also like