BADM 633 University of the Cumberlands Six Sigma Discussion

Content Type

User Generated

User

fvinabbevxnzny

Subject

Business Finance

Course

BADM 633

School

University of the Cumberlands

Department

BADM

Description

Task-1

Reflect on the assigned readings for Week and then type a 5 page paper regarding what you thought was the most important concept(s), method(s), term(s), and/or any other thing that you felt was worthy of your understanding. Define and describe what you thought was worthy of your understanding in half a page, and then explain why you felt it was important, how you will use it, and/or how important it is in project planning.

Task-2- Problem set (write 5 pages)

Discuss the following points regarding Six Sigma concept:

Discuss personal experience in regard to quality improvement programs and how they are project like in application such as DMAIC.

If you have no experience, you should gain some from friends or work colleagues or—as a last resort—news articles.
If news reports are used, references and in-text citations must be provided.

What has led to the more comprehensive strategic view about total quality management?
What impact did the quality improvement program have on the company or organization? Please provide specific examples demonstrating the impact.
Why do some quality initiatives fail?

Unformatted Attachment Preview

Scope Planning This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Scope Planning • • • • • • Defining the scope Project requirements Scope Inputs Requirements traceability matrix Work Breakdown Structure (WBS) Scope statement This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Project Scope • One of the main activities in the Project Planning phase is determining and documenting the project scope. • Project scope is the definition of all the work needed to successfully meet the project objectives. This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Deliverables • Must be described in a sufficiently low level of details This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Scope • Be as specific as you can • Where possible, the scope statements should include how the results will be measured so you and your sponsor will know with certainty whether that part of the scope has been achieved • Requirements should tie to things like the organization’s strategic plan and business objectives • Mention things that are explicitly NOT included: is this limited to certain locations? If in an international context, is it in only one language? This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Scope Not measurable Measurable A new registration system With the new system, students will be able to register for classes using a browser or a smartphone. The system will be fast Response time will be under 1 second The system will support the required volumes 75 students must be able to add an average of 3 classes each 15-minute period. Happy users User satisfaction will be measured by a standardized set of questions and will measure 5 or higher on a 7-point scale. This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Types of requirements • Functional • Non-functional • Performance • Development • • • • Technical Business User Regulatory This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Software requirements fundamentals • Unique challenges • Must be verifiable This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Measuring requirements • Each type of requirement may require a different type of measure: This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Scope inputs-techniques • • • • • • Interviews Focus groups Facilitated groups– JAD, QFD Group creativity techniques such as brainstorming Prototyping Observation • Questionnaires and surveys This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Scope Inputs-sources • • • • • • Project sponsor Management Strategic Plan Users Customers Competitors • Suppliers • Regulations • and others This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Requirements Traceability Matrix • Links requirements to their origin • Traces them throughout the project process • May link requirements to: • business needs, opportunities, goals, and objectives; • project objectives; • project scope/WBS deliverables; • product design; • product development; • test strategy and test scenarios; • or may link • High-level requirements to more detailed requirements. This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Simplified Requirement Traceability Matrix Code Description Source Priority Status 5 User interface must comply to company standard Corporate IT standards manual 1 In-progress 5-1 Help text uses corporate fonts Corporate style 2 manual 8-6 Include the users in the Project Charter, 1 testing item 7 This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). complete Project Management Chapter 9: Scope Planning Requirements Traceability Matrix fields • • • • • • Unique identifier Requirement statement Source Design specification reference Test specification Test case numbers • Remarks • … and more depending on the particular situation This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning WBS Creation • List all the project outputs (deliverables and other direct results); • Identify of all the activities required to deliver the outputs. • Subdivide the activities into sub-activities and tasks. • Identify the deliverable and milestone(s) of each task This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Creating the WBS • A list of all activities required to create all the deliverables in the scope. • Activities may be broken down into smaller tasks, in a hierarchical pattern • Do not focus on sequence or dependencies at this point This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Creating the WBS This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Creating the WBS • Follow a numbering plan • Can also be shown in outline format • May be very complex for a large project This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning WBS Creation Remember the 100% Rule: The combination of the boxes on each level represent 100% of the parent box. This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning WBS Creation • At the lowest level, the WBS consists of Work Packages • It is important that each work package is clearly defined and can be easily assigned • The work package level is where time estimates, cost estimates and resource estimates are determined. This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Scope Statement • Purpose: • Project deliverables • Major objectives • Measurable success criteria • Create and use a template suitable to your organization This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Scope Statement Typical Contents • Project Name • Project charter • Owner, sponsor, project manager, stakeholders • Problem statement • Project Goals and Objectives • Project Requirements • Project Deliverables • Exclusions • Milestones • Cost estimates This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Summary • Scope planning is an essential activity during the planning phase of the project • Provide relevant details and measurable deliverables in your scope • Use a Requirement Traceability Matrix to relate the deliverables to their sources and keep track of status • Create a WBS as a hierarchy • Remember the 100% rule . . . continued on next slide This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Summary (continued) • The scope statement includes • • • • • • • • • • Project Name Project charter Owner, sponsor, project manager, stakeholders Problem statement Project Goals and Objectives Project Requirements Project Deliverables Exclusions Milestones Cost estimates This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning Questions? This work is licensed under a Creative Commons Attribution 3.0 Unported License (CC-BY). Project Management Chapter 9: Scope Planning
Purchase answer to see full attachment

Tags: Six Sigma DMAIC Quality improvement quality initiatives improvement cycle

User generated content is uploaded by users for the purposes of learning and should be used following Studypool's honor code & terms of service.

Explanation & Answer

Attached.

Running Head: REFLECTION ON READING

Reflection on Reading
Institution Affiliation
Date:

1

REFLECTION ON READING

2

Indeed going through the reading this week has been one of the best things that have
happened to me in this whole course. There is a lot that I have learned all through, especially
on the scope matters in project planning and management. Essentially, there is a lot to do
with the concepts, ideas as well as methods and terms that everyone who takes the course
should always yearn to learn. It expands the expectations and the way one understands issues
at hand. Eventually, it is critically important to understand the importance as well as the
application of everything that has been provided throughout the week-long reading.
There are things that one needs to understand when it comes to project management.
The project is everything that needs the necessary guidance whenever it realizes the
objectives of the said project. However, to achieve the goals, the first and the foremost thing
is to understand the project scope. This includes defines the requirements needed to realize
the objective. The organization needs to limit the range to successfully follow it to achieve
the whole thing about the purposes (Watt, 2014). It will not be valid if, for instance, an
organization starts developing a project without a clear scope or without understands the
direction to which it is supposed to move. It matters a lot to define the scope and let it be
known to all the stakeholders to move in the same direction and at the same pace.
Scope planning, therefore, is a core activity in project management. Just the definition
of the scope may not be effective, but there is a need to understand the requirements as per
the range as well as the necessary inputs required to realize the objective. It is essential to use
various techniques to know whether the organization is following the scope requirement. This
helps to understand whether the threshold has been met or not. More importantly, it is good to
consider using a work breakdown structure to set the scope for every stage of the process
(Watt, 2014). Eventually, the scope statements are a practically important tool that ensures
that everyone is conversant with what is needed to realize the organization's needs and
requirements.

REFLECTION ON READING

3

One concept that everyone can learn from this is that scope is all about the main
activity in the project planning phase. Primarily, the range is written or instead develops right
before the operations are put in place. It is designed way before the project starts. It helps to
understand where to start and define the boundaries and the requirement necessary to meet
the needs. By identifying the essential scope, it will be possible to create an understanding,
especially on the project objectives. Such will be necessary for every stakeholder, as they will
understand the needed therefore, to hold on to every work or activity within the project that
defines the completion required.
One important thing that I have learned this week and especially perusing through the
reading is the importance of understanding the project's deliverables. It is essential to describe
the deliverables to know how to handle them sufficiently. The realization of the necessary
deliverables depends on the way individuals understand them. It is common to come across
the various types of deliverables as they relate to a specific project. In essence, the project
management and the organization will need to check on deliverables to understand whether
the organization is working on the realization of the project. The project deliverables must be
defined within the project start points to ensure the understanding is necessary, and there is
no problem with work...