ICT201 Assignment 2 Quality Management Plan : Control, Planning and Assurance for the MSS Project

1 INTRODUCTION

1.1 Purpose of the Quality Management Plan

This Project Quality Management Plan (QMP) documents the necessary information required to effectively manage quality issues from project planning to delivery. This QMP, therefore, defines the MSS project’s quality policies, procedures, criteria, areas of application, and the roles, responsibilities and authorities allocated to involved stakeholder.

1.2 QMP Components

The objective of this QMP is to help ensure that the MSS project is delivered in accordance with the identified specifications and stakeholder requirements.  It is intended that this QMP and the associated procedures will reduce the cost of quality by helping to avoid costly re-works, cost non-conformity, deficiencies, and unnecessary future maintenance and repair costs.

To achieve this, QM for this project shall focus on Project Quality Assurance (QA) to ensure quality management processes are in place and Quality Control (QC) to ensure that the delivered MSS platform and associated components are in line with the defined specifications and requirement.

2 QUALITY MANAGEMENT ROLES AND RESPONSIBILITIES

2.1 Specific Roles in the Organisation

The Project Quality Management Team (QMT) will be a part of the MSS Project Office (PO).  The personnel listed in Table 1 will be responsible for implementing Quality Assurance (QA) (including DC) and Quality Control (QC) across the entire team. The providers will be responsible for ensuring that our mandated QA and QC procedures are implemented effectively and in conformance with the requirements specified in the engagement contracts. The relationships between each of these roles are discussed in more detail in Section 3.

NOTE: DELETE ALL blue text after reading. All blue text are instructions for your guidance.

[Instructions for what to include in this section:  Put some careful thought into the development of this table.   Here are the key issues that you need to take into account:

• Ensure that the roles listed in Table 1 map to the ones shown in Figure 1. In other words, there should be a row in this table for every role listed in your organisation diagram.  This means that other roles will need to be added to this table. 
• Provide names of people who will be filling each role in the left-hand column of the table. Some of the names of people filling each of the roles have already been supplied in the Assignment information.  Where a name has already been provided for a role, please use that (in other words, read the Assignment 1 and Assignment 2 information carefully and apply the names that have been supplied).  For the Project Manager role, add your name.  For the remaining roles, add in any name you wish (e.g. you can use themed names, such as members of your team, world leaders, or movie stars).  There must be names provided for each role.  In the real world, this type of document must include a clear listing of people who will be responsible for each key QA role.
  
• The information already provided in the ‘Responsibilities’ column should be expanded to best represent the actual responsibilities associated with each role in the real world. You will get higher marks if you think practically about the issues and include other responsibilities that are inferred from other material associated with ICT Project Quality Management.  As an example, look carefully at Schwalbe and articles on the internet and then include these types of role/responsibility in the table as appropriate.  You will obviously get higher marks if your listing of responsibilities exceeds those supplied in the assignment information. As an example, the DC team would obviously also need to be directly responsible for developing the Knowledge Base and Service Desk Management System (SDMS) decision tree information and Frequently Asked Questions (FAQ) web site, as well as managing the Knowledge Base, Wiki, SDMS/FAQ content.

The more thought and effort you put into this table, the higher your score will be.]

Table 1:           MSS Project – Project Quality Team Members

 

2.2 Team Organisation and Lines of Responsibility

The relationships between the roles outlined in Table 1 are illustrated in Figure 1. These relationships and the lines of authority/responsibility are discussed in the following paragraphs.

[Instructions for building your diagram:  Build your diagram in a drawing tool and then import it into this document as a graphic.  At a minimum, your graphic should include all of the roles and lines of responsibility illustrated in the diagram discussed during the Topic 6 Workshop.  Please note that this diagram is not provided in the Workshop handout, so you will need to develop your own outline during the Workshop and then create the diagram for Figure 2 from those notes.  To avoid missing anything, make sure every member of your team develops the draft during the Workshop and then compare your notes afterwards to help ensure that you develop the right graphic.

Please note that the diagram discussed in the Topic 6 Workshop is not exhaustive and some roles that would be implemented in the real-world have been left out.  Therefore, have a think about any other roles that should be included and add these as you see fit.  You will get higher marks if you develop a more detailed organisational model.  However, remember that we just want to discuss those roles specifically focussed on Quality Management issues.  Consequently, do not just make a diagram that contains the entire organisational structure.  Base your organisational model on what was explained during the Topic 6 Workshop and expand on this as appropriate.

Lastly, make sure that the roles listed in your diagram are also outlined in Table 1, so there is a clear mapping between this section and the information provided in Section 3.1.]

Insert your Project Quality Management Team diagram here

Figure 1:          The MSS Project Quality Management Team

[Instructions for what to include in this section:  Below the graphic, you need to describe the key aspects of the relationships between the various roles.   In particular, cover:

• Lines of responsibility/authority. It will help if you begin by explaining the terms authority and responsibility and then putting these into the general context of this organisational structure.  Your discussion of the diagram must explain that people connected by the lines are responsible to their superiors in the organisational structure (e.g. those shown above in the diagram).  Additionally, make it clear in your discussion of the issues that those shown higher in the diagram have authority over those connected to them at a lower level.  The objective will be for you to outline the key relationships aligned to responsibility/authority in your discussion here (you don’t have to describe all of them in detail, just outline them in a broad sense).  When doing this, remember to make it clear that our contractors’ responsibilities are outlined in the contracts.  One final point about this.  All organisational interactions in the industry should aim to be collaborative.  Therefore, when discussing aspects of responsibility/authority, ensure that you avoid defining these as authoritarian relationships – outline them as cooperative relationships in which parts of the team have clear lines of authority/responsibility, so everyone can understand their defined roles.
• Escalation,The second key aspect must cover the concept of ‘escalation’.  As explained during the Topic 6 Workshop, escalation is the process of elevating problems to the next higher level in the hierarchy, to get issues resolved quickly.  You will need to use the Define, Explain, Apply approach to discuss this.  In other words, Define what is meant by the term escalation, Explain the practical implications, and Apply this by describing at least one example within the organisational framework that you have developed.

It is expected that you will complete this section in about half to one page of text.]

Insert your material here.

3  PROJECT QUALITY MANAGEMENT

Figure 3 provides an overview of the Quality Management Methodology (QMM) that will be applied to successfully deliver the MSS project.  This methodology is explained in more detail within the following paragraphs of this section.

Insert your Project Quality Management Methodology diagram here

Figure 3: An overview of the MSS Project Quality Management Methodology

[Instructions on what to include in this section:  Develop a synopsis of about 1 to 2 pages of text (not including your graphic), which explains how the project should ensure Quality Planning, Quality Assurance, and Quality Control.  Do this by taking the following steps:

• Carefully view the videos provided at the following web sites and make notes:

https://www.youtube.com/watch?v=cq22U4k5Ecg     (Quality Planning)

https://www.youtube.com/watch?v=84fpY8b2G10     (Manage Quality) (now Quality Assurance)

https://www.youtube.com/watch?v=SfoR2mLOBtk   (Quality Control)

QD, QC, QA: 3 Quality Processes… in 60 seconds (youtube.com) (3 Quality processes)

Quality Planning vs Quality Assurance vs Quality Control | Project Quality Management (youtube.com)

(Quality Planning vs. Quality Assurance vs. Quality Control)

• Develop a single diagram that illustrates the key points identified in these videos. Note that the quality management methodology/processes have evolved to Quality Planning (also known as Quality Design), Quality Assurance, and Quality Control. This diagram will obviously need to start with Quality Planning.  Then categorise the next parts of the model in terms of Quality Assurance and finish with Quality Control.  For each element, explain key inputs, tools, techniques and outputs that will be required in the following sections.  You will also need to include the relationship of these aspects with Quality Control and Quality Assurance.  When explaining how these three activities will be implemented, use the Define, Explain and Apply model to draft each section under its subheading.  In other words, begin each of the sections for the parts of your methodology diagram by:
  1. Defining what is meant by that section of the diagram (e.g., The first step involves conducting detailed planning for all aspects of Quality Management…).
  2. Explaining the broad implications of what that section of the diagram means (e.g., Planning Quality Management is an essential first step because it allows our team to determine optimal approaches for managing all aspects of quality within the project…)
  3. Applying that element of the diagram to our situation in the MSS project (e.g., The MSS project team will implement these processes early in the Plan Quality Management phase and will engage all involved stakeholders to define this critical element of our PM procedures…). Mention the activities that should be undertaken to achieve each aspect of quality management.
• Obviously, do not just copy the wording provided in the examples above. Put these into your own words.]

3.1 Quality Planning

Quality is the degree to which the project fulfils requirements. Quality planning determines quality policies and procedures relevant to the project for both project deliverables and project processes, defines who is responsible for what, and documents compliance. [Instructions on what to include in this section: In this section, write your proposed approach to quality planning – include any tools and techniques to be used]

3.2 Quality Assurance (QA)

The focus of quality assurance is on the processes followed in executing project activities. QA ensures that the right project processes are followed to produce quality deliverables. It involves following and meeting standards, continuously improving project work, and correcting project defects. [Instructions on what to include in this section: In this section, write your proposed approach to quality assurance – specify the QA processes and include any tools and techniques to be used – for instance, for a project process/activity like “Gather User Requirements” you may recommend a quality assurance activity of “Validate user requirements with business user group” – think about the quality assurance activities for each work element in your WBS]

3.3 Quality Control (QC)

The focus of quality control is on the project’s deliverables. QC monitors all deliverables to verify they are acceptable and achieve customer satisfaction. [Instructions on what to include in this section: In this section, write your proposed approach to quality assurance – specify the project deliverable and the QC tools and techniques to be used. Basically, for each deliverable you mentioned in the project charter, state how quality will be tested or validated]

4 PROJECT QUALITY STANDARDS AND GUIDELINES

The quality standards listed in Table 2 shall be applied for the MSS project.

[Instructions on what to include in the following table: Use this section to build up your understanding of key standards that you will need to apply when you are working in the industry.  Therefore, it is recommended that you put some rigour into completing this.  As you investigate the standards applicable to the four categories, you need to include the appropriate information in the columns.  Insert the information as follows:

• Standards to be Applied. In the left-hand column insert the standards/laws/regulations that are applicable.  When entering these, ensure that:
• you include the standard number where one is available and the title of the standard (as discussed in the Topic 6 lecture/workshop), or
• the entire title for laws and other general standards that do not have a standard number; and
• a web address for the site that contains the information on that standard.
• Equipment/Systems/Methods/etc. to which the Standards are applicable. In the right-hand column, list every key element of the systems or processes to which that standard/law/regulation would be applicable.   Keep these short, but make sure that it is clear from your description where that particular standard would be applicable (e.g. the Privacy Act would apply to the Client Data, including all personal information collected and managed). Alternately, where the standard is broadly applicable you can make a more general statement (e.g. for the ISO9001 standard, you would state something like: ‘All pertinent Quality Management processes applied within this project’).

It is recommended that you start working on this as soon as possible after completing the Topic Week 6 lecture/workshop and finalise this after a few weeks by merging the information that has been identified.  When doing this merge, make sure that you don’t double up entries, and rationalise the content so you create a single coherent listing.]

4.1 Project management/procedural standards. 

Project management/procedural standards.  Begin by looking at the standards that would be applied to manage the project formally.  As an initial hint – we have been talking about the most important of these throughout the semester.  Next, make sure that you include the various general quality standards that will be applicable (e.g. ISO 9000 and the others discussed in the Topic 6 lecture).

4.2 Product/System Standards

Product/System Standards.  There is a wide range of system standards with which we are going to have to conform.  The easy starting point for defining these is to look at the technical architecture overview information and then investigate key standards that will be appropriate for each system element, application and interface – consider network requirements (e.g. standards for RTSP, TCP-IP, ODBC, etc.).  This can be done through the websites discussed during the Topic 6 lecture/workshop and by doing some additional internet research. Operating Systems.  In parallel with your investigation of the preceding standards, make sure that you consider the various operating systems for which we will need compatibility in the MSS.  May include Windows, Mac iOS, Android, and others.

4.3 Laws and Regulations

Laws and Regulations.  Think about key laws and regulations.  For this project, these would include the following: Competition and Consumer Act 2010 (Cth), Freedom of Information Act 1982, Leadership and Service Management – Standard 7.3, Privacy Act 1988 (Cth), Spam Act 2003 (Cth), and Trade Marks Act 1995 (Cth).  When investigating these types of laws/regulations, you may also replace the Australian laws with similar pertinent legislation in your country and list those within the following table instead.

 

5 PROJECT TESTING

5.1 Overview of the Testing Regime for the MSS Platform

The detailed project testing approaches, strategies, and techniques are explained in the associated Test Plans.  However, the general principles that apply to this project include the information provided in the following subsections.  The table in Appendix 1 also maps how key functional and non-functional tests will be implemented during the project.

[Instructions on what to include in this section:  In this section, you need to include a practical overview of the steps that you will apply within the preceding testing regime to conduct the testing of the MSS platform.  This does not need to be too long (typically no more than one to two pages of text).  Make the discussion of the issues as practical as possible and consider all necessary types of tesing.

Unit Testing, System Testing, Integration Testing, and Acceptance Testing.  Acceptance testing will be conducted in the operational environment.  Obviously, you would need to define all of the various tests that will need to be conducted within a Test Plan.  This would typically be similar to the one developed for system testing, but additional tests will be required to assess a wide range of different demand types by the users.   For instance, extensive load testing scenarios will be required, and usability testing will need to consider various ethnic/ cultural variations.   The setup for these acceptance tests will also be somewhat different.  As an example, you will need to get buy-in from stakeholders through site visits prior to the sessions, and you would have to ensure that assistance can be provided to help them conduct the tests (therefore, prior training and support throughout the process will be necessary for the users involved in the testing).  Additionally, you would need to drive the testing around the client/tester work cycles.  This can have a very significant impact on the way you would coordinate/manage the tests. 

Please note that the preceding listing does not include all of the factors that you would take into account.  Additionally, it would be upsetting to just see the same information included in your QMP response.  What is expected is that you will think about these issues and provide a relatively short and focused description of the approach that would be taken (in your own words).  Just as importantly, when considering these issues, think about:

• who will conduct the testing at each stage (Hint: think about Test Plans and the responsibilities/authorities you described in Section 3 of the QMP ;
• when will the testing be carried out (think carefully about some of the preceding issues);
• where will the testing be conducted; and
• how will the testing be managed and coordinated (Hint: think about Test Plans and the responsibilities/authorities you described in Section 3 of the QMP and the locations of the test sites)

Please note that there is no need to develop specific Test Plans or budgets.  All that is required is that you provide a clear synopsis that demonstrates that you have considered some of the key practical issues and you are able to explain them clearly and succinctly.]

You should develop the material defined by the following points.

• Functional Testing. This material should be completed in Section 1.1.  Begin this section by defining what we mean by functional testing.  Then define each of the different types of functional tests outlined in the Topic 6 lecture (e.g. unit, integration, system, and acceptance).  When doing this, use the Define, Explain and Apply model.  For example, you would define what we mean by unit testing, then explain what it is designed to achieve, and finally, you would apply this to the MSS situation, by giving at least one example to describe where unit tests would be conducted in the project.
• Non-Functional Testing. This material should be provided in Section 1.2 and should cover Availability, Compatibility, Compliance, Configuration, Interoperability, Security, Performance, and Usability testing.  Before discussing what is meant by each form of testing, begin by explaining what is meant by the term ‘non-functional tests’.  Next, for each of the required non-functional tests, use the Define, Explain and Apply framework to explain each of these. 

Short Scan Bullet Point (SBP) descriptions will suffice for the descriptions of the various functional and non-functional tests.  To demonstrate the concept of the SBPs, some have already been provided in Sections 6.1.1.  Obviously, you will need to replace the associated text by adding the required material in the Define, Explain, Apply structure.  You will need to replicate this approach in Section 6.1.2.  To assist in the creation of new bullets of this type, you can use the List Bullet Style and you can create sub-bullets using the List Bullet 2 Style (Note:  all of the key styles that you will need are provided in the Styles section shown in the ribbon).

When completing these SBPs, ensure that there is enough information included to allow a novice (someone who does not have any knowledge about ICT testing) to understand the principles.  Feel free to develop diagrams as appropriate.  It is expected that you should be able to complete Sections 6.1.1 and 6.1.2 in about one and a half to three pages of text.  The more detailed and understandable your response (within reason – i.e. don’t waffle) the higher your mark will be.]

5.1.1 Functional Testing

Insert your answers here for the lead-in material mandated above.  Make sure that you also introduce the SBPs with a statement such as ‘The following are the key functional tests that will be applied within the MSS project:’.

• Unit Testing. Replace this text, by inserting your description using the Define, Explain, Apply approach (which is explained above).
• Integration Testing. Replace this text, by inserting your description using the Define, Explain, Apply approach (which is explained above).
• System Testing. Replace this text, by inserting your description using the Define, Explain, Apply approach (which is explained above).
• Acceptance Testing. Replace this text, by inserting your description using the Define, Explain, Apply approach (which is explained above).

5.1.2 Non-Functional Testing

Insert your answers here on non-functional  tests

Appendix I

The symbols in the cells of this table mean the following:

ü or Yes = This type of test would normally be applied for this element of the testing regime

? = This type of test may be applied to this element of the testing (but it will be situation-dependent)

Blank = This type of testing is typically not done for this type of functional testing.

 

 

The post ICT201 Assignment 2 Quality Management Plan : Control, Planning and Assurance for the MSS Project appeared first on My Assignment Help SG.