CSS 559 Assignments and Due Dates

Through the course of this class you will be writing your project proposal. The following are due dates for consecutive pieces of the proposal. Please add each as a new section on a single document and turn in the whole document each time you turn something in so that I can see how the whole proposal is progressing. I expect that with each iteration you will be making edits and improvements based on feedback from me and your advisor. With each class period come prepared with a 1 – 2 PowerPoint slide summary of the section (or as many as you want to put together for that section). These will also add to each other so that you will be building your presentation at the same time that you build your written document.

1. Project Introduction / Overview / Background, Project Goal or Purpose (Due January 23 or 30) (5 points)

State the reason the project is being undertaken. Provide a background and a case for the project that is grounded in what has come before that describes the problem or issue this project will seek to resolve.

Be specific as to how this project came about and why it is important. Why should we care about this project? Make a compelling and scholarly argument for the project and what it will accomplish.

Provide clear, concise goal(s) statement(s) for the project or scope of work. What is the purpose of the project? What research or evaluation questions are you seeking to answer?

Spend time developing the goals and objectives for the project. Understand and clarify the beginning and end of the project. Avoid projects that have unclear or fuzzy deliverables. Select projects that have specific outputs and unambiguous results. All effort for the project should be directed toward the goals and objectives. You will complete a logic model for your project that will help you to clarify these things. You may choose to include this in your proposal.

2. Review of the Literature and Theoretical framework (Due February 13 or 20) (25 points)

Provide a review of literature relevant to your project goals and methods.  This should include theoretical and/or pedagogical frameworks, reviews of similar projects, and findings from previous related research.

3. Project Approach/Methods (Due March 6 or 13) (25 points)

State the proposed approach or methods that will be used to meet the project goal(s). Examples might include, but not be limited to, the development of an artifact, prototype, design, applied research, or concept, etc.

Provide a detailed procedure with evaluations and controls. Make sure to include time and effort for the project manual/write‐up, committee reviews, defense, etc. Link this to milestones or the project schedule in some way. Is your process congruent with your deliverables, schedule, and milestones? Does it result in the outcomes and stated objectives?

4. Proposed Analysis (Due April 3 or 10) (25 points)

Explain how you will analyze your data and / or evaluate the success of your project.  For example, if you are comparing learning outcomes between two groups of learners and you propose to do a pre- and post-test design to look at changes in content understanding, what statistical analysis will you do to help you make a determination of the significance of differences from pre to post or between groups?  Or, if you have designed a resource manual for a community planning process, how will you evaluate the effectiveness of the tool?

5. Project Deliverables / Expected Results, Requirements / Resources / or Identify Process, Assumptions, Limits and Exclusions, Milestones (Think of this as your work plan) (Due April 13) (20 points)

List the products or services that are the intended outcomes to be produced in order to fulfill the goal(s) of the project. Deliverables should have measurable results and be specific in terms of what will be presented and documented at the project defense.

Enhance and detail the expected results from a deliverables point‐of‐view. What will the committee see/touch/receive as a result of this project? Not just the general benefits or outcomes, but the tangibles (i.e., documents, reports, artifacts.)

List the specifications for each deliverable, which may include quality, quantity, or use of specific products/components. List the critical success factors required for project success at completion.

Be specific in listing the actual resources you will need (e.g., equipment, people, software, knowledge, supplies, etc.) Obviously, we don’t care that you are using a #2 pencil, but do provide pertinent details and allocate resources so they are congruent with the project schedule.

List all conditions believed to be true before beginning the project. Examples might include assumed access to facilities and/or equipment, planned delivery dates, or partner involvement. Assumptions are items that you expect will hold true now, and throughout the duration of the project.

Specify project limitations and delimitations. Define the items/products/services that are not part of this project. Clarify items /products / service/deliverables that may be produced to minimum levels. Be specific about what will NOT be included.

Provide an estimated project schedule with milestones and completion dates.

Even through you will have dates on your project schedule, also place dates on the milestones listed on the proposal. You may want to develop a Work Breakdown Schedule (WBS) to make sure that you have allocated the work effort correctly. What activities, milestones, and controls are included so that you know that you have successfully completed the objectives?

Leave a Reply

Your email address will not be published. Required fields are marked *