2) Define or Accept the Service Master role.
3) Divide the rest of the roles among all members of the group: Process Master, DevOps Engineer, Release Coordinator, Development Team, Operations Team. Be sure to respect the two pizzas rule. You can choose not to assign a certain role, if you have a valid reason for that.
4) Once you have the team assembled and each role understood, you’ll have to select one of the three projects your team will take over the responsibility to deliver.
5) After selecting the project you’ll have to communicate this decision to the CEO, securing all the support and resources you might need to produce a good DevOps approach.
6) Once you got formal approval, you’ll have a kickoff meeting where Zyx stakeholders and each team member should have a clear understanding of the expectations and what needs to be done and when.
7) Each team then will work to produce the definitions, tools and deliverables expected in DevOps to hold a proper Planning Meeting which is the final Deliverable of this practical assignment.
8) Evaluation: provide feedback to each other and on the final results.
Deliverables
• A documented project approval with specific resources allocated
• A Kickoff meeting script to communicate Project goals, expectations, stakeholders, dates and definition of done
• Planning Meeting document with definitions, tools and expected deliverables
Time allowed
3 hours
Practical Assignment Day 2
Context
The DevOps Master™ must be able to analyze the DevOps process and indicate aspects that are missing, erroneous or to be improved regarding continuous integration and continuous deployment. This assignment is about these analyses.
Assume that Continuous Integration and Continuous Delivery are implemented.
Your assignment
1) Your teacher will play the role of the Process Owner.
2) Other candidates or co-workers of the candidate may act as the Development Team and Operations Team.
3) Define or accept a scenario with all relevant information of one DevOps project.
4) Define or accept a new project (scenario) to create an impact analysis of Continuous Delivery.
5) Produce the required analyses for each aspect of the project.
6) Present a document with your analysis to the Process Owner, explain your findings and its reasons.
7) Evaluation: provide feedback to each other and on the final results.
Deliverables
1 Analysis of how Continuous Integration fulfills the following aspects
• List of evidence that specs are realized, and processes are followed (Competence B2.1, B2.4)
• List of evidence that the integration standards are followed (Competence B2.2)
• Matrix of integration test cases and components or software (Competence B2.3)
1 Analysis of Continuous Integration, including the following aspects:
• describe the recommended Continuous Testing process (Competence B3.3), test programs (Competence B3.1) and organization of test programs (Competence B3.5)
• a test plan for one sprint (Competence B3.2)
• list the deviations in the user stories from the scenario (Competence B3.4)
•
1 Analysis of the user stories for a new project, including:
• a list of the possible negative effects caused by the current delivery pipeline (Competence B4.1)
• an indication of which build, and deployment scripts needs to be adjusted. (Competence B4.2)
• a list of the activities to be performed in order to adjust the delivery pipeline (Competence B4.2)
• a list of the standards and procedures to be used in order to let the delivery pipeline work as expected (Competence B4.3)
1 Definition (or analysis of the completeness of the usage) of the following stories for a project:
• User stories based on:
• List of service levels, business processes and impact on users (Competence C2.1)
• List of functional specifications (Competence C2.2)
1 Analysis of the effectiveness of the problem management aspects within a DevOps process
1 list of actions to minimize the business impact of the escaped defects (Competence C4.1)
• should be related to the Business Continuity Support and stated Risk Assessments in the SLA
1 list of alternative actions that have been considered (Competence C4.2)
• Including the risk mitigations present in the current Risk Assessment
1 forecast of service outages due to the currently known escaped defects (Competence C4.3)
1 description of the performance of systems or components that are optimized by the operation team
• Describe how this fit within the DevOps process (Competence C4.4)
Time allowed
3 hours
Practical Assignment Day 3
Context
The DevOps Master™ must be able to monitor the technology. He or she has to be able to innovate the DevOps process including the development of involved personnel.
Your assignment
1) Your teacher will play the role of the Process Owner.
2) Other candidates or co-workers of the candidate may act as the Development Team and Operations Team.
3) Define or accept a roadmap of tooling
4) Define or accept a DevOps process with a given DevOps maturity.
5) Produce the required plans and presentation.
6) Present to the Process Owner, explain the business benefits and the plans.
7) Evaluation: provide feedback to each other and on the final results.
Deliverables
1 Innovation plan, including
• a roadmap planning of the implementation of new technology and adaptation of emerging technologies in order to:
• create new solutions (Competence A7.1 and Competence A9.2)
• integrate new technology into existing products, applications or services (Competence A7.2 and Competence