Quality Review of a project

Quality Review

Group Number:      

Unit:                    

Student 1:              

Student 2:              

Project Mentor:     

Date:                 

1         Overview

1.1         Which group did you review?

<Group 10- cloud migration for charity>

1.2         Which artefacts did you review?

Technical artefact3:<password construction guidelines>

  • Technical artefact4:<Password protection policy>
  • Technical artefact5:<Application security policy>

1.3 Project Summary

<This project will be about transferring the entire data of an organization known as “Save the Children’ onto the cloud platform that will also be created by our team only. This project will help the client organization in moving their entire information and data with utmost safety on cloud platform from the traditional on-premise storage database.

As per the requirements of the organization Save the Children, the proposed architecture should be scalable and reliable along with the efficiency of the cost. The proposed system should also facilitate the organization in smoothly reaching the targeted audience. The designed architecture will help the management team of the charity organization in reaching the goals with better security, faster speed, and easy accessibility to the different resources. For accomplishing this task of finishing the project effectively, the team working on it must possess the good knowledge and practices of learning and implementing the Learning Solutions.

In this project, the creation and deployment of the cloud-based architecture will be done that will help the charity organization Save the Children in shifting their entire information and database on the cloud platform from the traditional on-premise architecture of storing the data.

2         Technical Artefact 1 Review

2.1         Technical Artefact Title

<Disaster recovery plan policy>

2.2         Technical Artefact Summary

<><In this artifact, the discussion is carried out on the implementation of different policies in the system of the organization that will help them in mitigating the risks caused due to the various disasters. In this policy, the plan will be depicted for recovering the organizational data in the case of disaster occurrence. The creation of this particular plan will facilitate the management team of the charity organization Save the Children in dealing with the various contingencies of disasters and get more benefits in the competitive aspects.

The plan provided in this policy will facilitate the charity organization Save the Children in saving information and the IT Systems from the data losses caused due to the occurrence of the unexpected event of any disasters. For the development and testing of this plan, the staff of the IT Management will be responsible and accountable.>

2.3         Strengths

< The different strengths and positivities of this technical artifact of ‘Disaster Recovery Plan Policy’ areas listed below:

  • This policy or the plan will save the organizational data from the various outages caused due to the sudden occurrence of different accidents and disasters.
  • The delays in the implementation of the different of different plans and activities can be avoided with the creation of this particular plan for outage mitigation.
  • Best and appropriate practices are being carried out for implementing effective collaboration and communication between the different teams associated with the project of deploying and creating the cloud architecture.
  • Very good and faster speed of restoring the major and key resources and tools required for the execution of the further processes and operations by the organization.>

  >

2.4         Weaknesses

<> The different weaknesses and negativities of this technical artifact of ‘Disaster Recovery Plan Policy’ areas listed below:

  • The recommended plan of the proposed policy is not adequately tested.
  • Requirement of highly skilled and motivated staff members.
  • Provision of inefficient data backup on the regular basis.>

2.5         Recommendations

<The various recommendations that can be made to the organization in respect to the implementation of ‘Disaster Recovery Plan Policy’ are as follows:

  • Proper and adequate testing of the proposed artifact needs to be conducted before its actual implementation into the system.
  • An accurate and effective system for taking the backup of the entire organizational data must be imposed.

All the practices and processes of adverse publicity of the system need to be avoided  >

3         Technical Artefact 2 Review

3.1 firewall policy rules

3.2 Technical artefact summary

Technical Artefact Summary This artifact is related to the discussion over the different rules that need to be considered for protecting the different policies of different Firewalls. Here, in this artifact, different configurations or the protocols of the firewall system are explained as per their priority and the designation in the rank sheet.

As the priority list of the firewall rules, traffic blocking through the default has been considered as the priority, and after that falls the entire traffic that is specified in the system.

3.3         Strengths

The different strengths and positivities of this technical artifact of ‘Firewall Policy Rules’ are as listed below:

  • All the rules related to the security protocols from the firewalls are explained effectively as per the priority list.
  • All the aspects of the system firewalls are explained with proper and effective descriptions for easy and appropriate implementation in the system.
  • This artifact has explained the entire procedure in a proper executable manner.

3.4         Weaknesses

The different weaknesses and negativities of this technical artifact of ‘Firewall Policy Rules’ are as listed below:

  • This artifact has a lack of explanatory data related to the different aspects.
  • A detailed description of the different ports of firewalls is missing.

3.5 Recommendations

The various recommendations that can be made to the organization in respect to the implementation of ‘Disaster Recovery Plan Policy’ are as follows:

  • More effective and detailed data can be provided.
  • The effective rule book for the implementation of the same should have been explained in this artifact for better presentation and explanation.

4         Technical Artefact 3 Review[SG5] 

4.1         Technical Artefact Title

< Password construction policy>

4.2 Technical artefact summary

Technical Artefact Summary This artifact is purely based on the different protocols and processes that will be required by the system of any organization for constructing a strong and effective password. It is mandatory for the individuals as well as for the organizations also to keep their important data secured and safe from external threats and attacks. The strong passwords will facilitate all the users of the organization to secure the data and information they will be stored on the new proposed cloud architecture.

For constructing a robust and strong password, the users can utilize different aspects such as combinations of words and numerals, numerals with special characters, etc. in most of the case, the stronger password can be created by using more characters, that is at least 8 characters will be required for constructing the stronger password.

4.3Strengths

The different strengths and positivities of this technical artifact of ‘Password Construction Guidelines’ are as listed below:

  • These guidelines will facilitate the users and the organizations to secure their data and information stored on the different platforms.
  • The users will be able to generate strong passwords for their data by going through these guidelines.
  • Breaching of the personal and confidential data of the organization will be avoided.

4.4Weaknesses

The different weaknesses and negativities of this technical artifact of ‘Password Construction Guidelines’ are as listed below:

  • The longer passwords will be harder to remember by the users.
  • The user will not be able to utilize their older passwords after resetting them.
  • Attempts of unsuccessful login attempts will lead the users to get lockout from the system for a particular period of time.

4.5Recommendations

The various recommendations that can be made to the organization in respect to the implementation of ‘Password Construction Guidelines’ are as follows:

  • The approach of constructing the password can be improved by implementing the practices of authentication.
  • Provision for utilizing the older passwords.
  • The limit of 8 characters needs to be reduced.
  • Technical Artefact 4 Review
    • Technical Artefact Title

<Password Protection Policy>

  • Technical Artefact Summary

This policy will let the users and the accounts protect their passwords from getting lost or incorrect. The protected passwords will let the different individuals related to the services of the organization maintain their privacy and security.

This policy of password protection will facilitate the users and the other individuals of the organization Save the Children to protect all their confidential data by securing their passwords from getting compromised.

The users and the organizational management teams will get to learn about the different rules and regulations that are to be followed for protecting their passwords in an effective manner.

  • Strengths

The different strengths and positivities of this technical artifact of ‘Password Protection Policy’ are as listed below:

  • This policy will let the users implement different protocols to secure their data and information stored on the cloud.
  • This will let the organization to protect its network with effective controls and protocols.
    • Weaknesses

The different weaknesses and negativities of this technical artifact of ‘Password Protection Policy’ are as listed below:

  • More adaptive methods of compliance verification need to be implemented.
  • Lesser utilization of the multifactor authorization.
  • All the rules and regulations are not followed appropriately.
    • Recommendations

The various recommendations that can be made to the organization in respect to the implementation of ‘Password Construction Guidelines’ are as follows:

  • The reset timings for the passwords need to be made limited to 180 days.
  • The complexity and the length of the passwords need to be reduced for making them more protected.
  • The encryption of all the passwords needs to be provided or saved in the database of the organization or the server for getting them back in the case of an emergency.
  • Technical Artefact 5 Review
    • Technical Artefact Title

<Web Application Security Policy>

  • Technical Artefact Summary

This policy has been created for assessing all the security protocols utilized for protecting the functionality of web applications. This will help the charity organization Save the Children in maintaining and prevailing the security compliance, postures, altered technological controls, and risk management.

For conducting this assessment for the charity organization Save the Children, all the contracted and employed security personnel will be responsible that are part of the organization Save the Children itself. The various updates or the releases of different applications will be managed and assessed according to this policy.

  • Strengths

The different strengths and positivities of this technical artifact of ‘Web Application Security Policy’ are as listed below:

  • This policy will let the charity organization Save the Children in assessing the different risks that are being encountered with their web application.
  • This policy will let the organization and the users of the services provided by the charity organization Save the Children in improving the functionality and security of their web application.
  • This will facilitate the charity organization Save the Children in implementing the different protocols and procedures to release the new web application.
    • Weaknesses

The different weaknesses and negativities of this technical artifact of ‘Web Application Security Policy’ are as listed below:

  • If not implemented properly,  the security of the proposed web application of the organization will get compromised.
  • Documentation of the assessed risks needs to be done at each step for better implementation and functioning of the protected web application.
    • Recommendations

The various recommendations that can be made to the organization in respect to the implementation of ‘Web Application Security Policy’ are as follows:

  • The timelines for the different releases should be defined.
  • All the processes need to be conducted on the basis of proper guidance and with faster actions.
  • Utilization of different tools should be done for getting better and effective results for the protection and security of the web application.
  • Project Review

For the execution of this project management practice, the different artifacts that have been considered by the group are as follows: Disaster Recovery Plan Policy, Firewall Policy Rule, Password Construction Guidelines, Password Protection Policy, Web Application Security Policy. In this project, the discussion has been carried out for the safe migration of the entire data that belongs to a charity organization known as Save the Children to the cloud architecture from the traditional on-premise architecture. This shifting of the data will facilitate the organization and its management team in securing all the important and confidential information. The considered organization of charity, Save the Children works in the field of enhancing the education and health of children from all over the globe. The implementation of the cloud architecture for their data security and storage of the organization Save the Children will help them in being more cost efficient with the scalability and reliability of the operations or services they are executing. The group that has executed this project has considered almost every aspect that is important for the process of migrating the organizational data from the traditional on-premise platform to the new and robust platform of cloud architecture. The security and safety protocols of the system are also considered effective in this project. All the work is executed on the basis of facts and actual data.

  • Evaluation

Give a rating for each item by placing an X in the appropriate box.

 Much better than our groupSlightly better than our groupAbout same as our groupWorse than our group
Quality  X 
Depth and details  X 
Presentation X  
  • Reflection: How do you recommend your group improves?

Based on what you have seen from another group, explain what you can do differently in your project to improve.

As per the presentation provided by the other group, I would like to make the following recommendations for my team such as:

  • For all the different aspects, proper and appropriate data needs to be provided. This will help in an easy explanation of the topic and the project as well.
  • The proper and effective documentation of all the discussions needs to be attached and mentioned in the project plan.
  • Time and duration need to be considered for the execution of the project along with the other constraints related to the completion of the project.
  •  All the rules and regulations need to be followed at every stage of the project for its better and inline execution and to reach the results in an effective manner.
  • All the information and data related to the project execution needs to be backed up for the conditions of emergency or the occurrence of an accident.
  • A descriptive approach for explaining all the different aspects should be followed in the project for defining them and get more effective results.
  • Proper compliance needs to be followed at any cost for avoiding unnecessary misconduct.
  • Proper testing of all the deliverables should be conducted for avoiding the issues that occurred during the final implementation.
  • All the data and information collected for the execution of this project needs to be sourced from reliable and effective sources.
  • Appropriate and effective tools should be utilized for executing the different operations and functions in the system.
  • An authentic and proper plan needs to be created for project execution and should be followed strictly for reaching the results easily, and early.

 [SG1]This template contains sample or explanation text inside <angle brackets>. You should fill in with the correct information or delete the explanation text when not relevant. For example, you would replace <Project Title> with the title of your project (and delete the <angle brackets>). This is NOT the title of the project under review.

This template also includes examples. You must delete the examples before submitting your report.  When tables are used, add/delete any rows where necessary.

 [SG2]All review teams have access to the Project Plan and Draft Presentation. Therefore, you need to add the titles of technical artefacts that were provided to you by the Unit Coordinator. For example:

Project Plan

Draft Presentation

Technical artefact 1: Wireless Network Design

Technical artefact 2: Password Policy

Technical artefact 3: Risk Assessment Results

Some review teams may have a different number of technical artifacts assigned to them. Add/delete dot points where necessary.

 Note: The length of your review depends partly on the length of the technical artifact. Most technical artifact reviews will be about 1 or 2 pages of text. If a technical artifact is short (e.g. a 2-page policy) then the review may be short (about 1 page). If a technical artifact is long (e.g. a 30-page design document) then the review may be long (about 2 or 3 pages). Reviews will be longer if you include diagrams or screenshots.

 The number and depth of recommendations will be dependent on the quality of the technical artifact.

In all cases, some recommendations are expected.

In cases when you have identified a lot of strengths (but not many weaknesses), i.e. you think it is a great technical artefact, then there may not be many recommendations. But there should be many project reflections at the end of the review.

In cases when you have identified a lot of weaknesses (but not many strengths), i.e. you think it is not a good technical artefact, then there should be many recommendations and they should have depth. However, there may not be so many project reflections at the end of the review.

 If you have more than three (3) technical artefacts to review, simply copy and paste section 4 as many times as needed. If you only have 1 or 2 technical artefacts to review, then simply delete the unnecessary sections.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s