Client Profile And Project Proposal

/in /by

PHASE I INDS 470 | SCAD | FALL 2021

PHASE I: CLIENT PROFILE In this project you are asked to research and identify the project’s client. A client should be an organization that

would realistically fund the project. It is important to note that they may or may not be the organization running

the facility. For example, if you are proposing a homeless shelter for veterans, your client might be The U.S.

Department for Veterans Affairs, but they would not be the people working in the facility and handling the

day-to-day operations. The VA would be providing the grant money for organizations like yours, the organization

funding the project might be the “Vietnam Veterans Workshop.” In order to justify your client selection, you

should include the following information in the profile:

● Name of organization and logo ● Location ● Company organization and background ● Budget constraints ● Precedent of partnerships/charitable work/grant funding ● Statement of why they are investing in your project ● Their goals for your project and how they might align with your goals

STUDIO V: CAPSTONE Page 1 of 1 Prof. Catie Pizzichemi

Locate a research study that utilized experimental or quasi-experimental methods

/in /by

  Locate a research study that utilized experimental or quasi-experimental methods. Briefly summarize the study. For example, discuss the inclusion of 2-group tests, regression analysis, and time-series analysis in terms of the study design’s strengths, weaknesses, or limitations. What challenges or limitations did the researcher identify they encountered by choosing this method?

Embed course material concepts, principles, and theories (which require supporting citations) in your initial response along with at least two scholarly, peer-reviewed journal articles. Use APA style guidelines.

Visualiation

/in /by

Select any example of a visualization or infographic, maybe your  own work or that of others. The task is to undertake a deep, detailed  ‘forensic’ like assessment of the design choices made across each of the  five layers of the chosen visualization’s anatomy. In each case your  assessment is only concerned with one design layer at a time.

For this task, take a close look at the annotation choices:

  1. Start by identifying all the annotation features deployed, listing them under the headers of either project or chart annotation
  2. How suitable are the choices and deployment of these annotation  features? If they are not, what do you think they should have been?
  3. Go through the set of ‘Influencing factors’ from the latter  section of the book’s chapter to help shape your assessment and to  possibly inform how you might tackle this design layer differently
  4. Also, considering the range of potential annotation features, what would you do differently or additionally?

Submit a two-page document answering all of the questions above.   Be sure to show the visualization first and then thoroughly answer the  above questions. Ensure that there are at least two-peer reviewed  sources utilized this week to support your work.

Assignment 2

 

ind  a peer-reviewed scholarly journal article discussing electronic  innovation and the government. Complete a review of the article by  writing a 2-3 page overview of the article. This will be a detailed  summary of the journal article, including concepts discussed and  findings. Additionally, find one other source (it does not have to be a  peer-reviewed journal article) that substantiates the findings in the  article you are reviewing.

You should use the UC library (https://www.ucumberlands.edu/library) and/or Google Scholar to find these types of articles (https://scholar.google.com/ )

Once you find the article, you will read it and write a review of it.  This is considered a research article review.

Here are many ways to develop a Work Breakdown structure.

/in /by

.  There are a few approaches that can be used to develop a Work Breakdown Structure (PMBOK, 2017).
Using Guidelines: Past projects can be used as templates to create a WBS for the current project. There could be other documentation created for this specific project that could be used to create the WBS. Essentially, guidelines are a method in which project-specific documentation and resources are used to create the WBS for the current project.

Top-Down: This approach allows the project manager to start with the larger aspects of the project to break them down into smaller components that can be easily managed.

Bottom-Up: This approach is the opposite of the top-down approach, in that the project manager can start with team members, small tasks, and activities. Afterward, larger categories and groups can be created until you are found with a completed project.

2.  I prefer theTtopdown Approach liking the top-level review first, and then having the creation of items and tasks required. Do you prefer one level over the other?  Do you anticipate using the Analogy approach is a factor?

“Analogy Approach – This involves review and analysis of the WBS of similar projects previously executed, to customize and adjust to the needs of the current project. This approach accelerates WBS creation,” (Lewinson, 2012).”

3. The deliverable-based approach is something I’ve always used as so much of the software industry is centered on building a product.  (thus, the “deliverable”).  From there, the top-down approach has been a staple of almost every project shop I’ve been in.  It might be, and probably is different for other industries, but beginning with the big stuff and working your way down to the task level is 100% the easiest way to approach building a WBS.

Regarding the analogy approach, I think that’s where we get into developing templates (whether for the WBS itself or for project plan skeletons).  We both are now several classes into the PM program, and historical performance data has popped up in each class thus far.  In terms of applying it to the WBS, historical data use can really shorten the WBS build process if the work is similar enough from one project to the next.  Still, it’s not a bad idea to have a WBS skeleton (format) as a general source.  That keeps builds and documentation aligned across many projects.

As you’ve mentioned above, I can get benefits from combining the analogy approach (even if time is not a factor) and the top-down approach, because it may add continuity across the projects where appropriate.

4.  There are many ways to develop a Work Breakdown structure. The three commonly used I have selected are as follows:

The Top-Down Approach – this is one of the most well-known methods commonly used. During this approach, you identify the most significant or largest task in the project and break down from there.

The Bottom-Up Approach – another common method used, but instead of starting with the most complicated task, you start with the easiest task and complete it first. This is an excellent method for brainstorming a solution to the problem (Mukund, 2017).

Guidelines – this is one of my favorite approaches, because it sets the guild lines for how to create the WBS and makes planning each part easier.