Les formations Scrum

Scrum Training

Formations à la Gestion de Projet avec Scrum

Plans des Formations Scrum

Identifiant (ID) Nom Durée Vue d'ensemble
45 Agile Project Management with Scrum 14 hours Who should attend? This 2 day course is suitable for any IT professionals who are interested in implementing Iterative Agile and Scrum methodologies to manage software development. This course is particularly suited to project managers, team leaders, developers and customers of software development wishing to have a stake holding in the development process. Why Agile? Comparison of iterative methodologies Why things go wrong The Agile approach What is Scrum? Pigs and chickens Product owner The customer representative Prioritizing product requirements Writing effective stories Acceptance criteria Negotiating sprint contents Group exercise to produce customer requirements and write stories based on the requirements The sprint Sprint backlog Sprint planning: what to do Sprint planning how to do it What happens during a sprint Burn down charts Group exercise to plan a sprint Scrum Master Implementing Scrum Ensuring proper practices Maintaining documentation Standup meetings When to pair program Group exercise to implement Scrum Finishing a sprint Scrum review meeting Scrum retrospective meeting Releasing an iteration Group exercise the review a sprint Is Agile and Scrum for you? Review of the Scrum process Comparison with other methodologies Benefits of pair programming Group exercise to discuss which aspects of Agile and Scrum can be applied to attendees organisations
511 Scrum Product Owner 7 hours This course is for: Product owners, managers, or anyone interested in Agile planning and estimating techniques. The course, Scrum Product Owner (SPO), utilizes a combination of presentations, discussions, and hands-on exercises explaining and demonstrating through practice. It illustrates what it is like to take on the role of an Agile team. The course covers all aspects of a product owner's involvement in an Agile product's life-cycle, such as gathering requirements rapidly, writing user stories, estimating story points, tracking, release planning, reporting, forecasting, scaling, and so on. How to be an effective Product Owner The Duties, Rights, Privileges The Promoting self-organizing teams How to Write User-Stories (Agile requirements) Establishing and Knowing your stakeholders Looking at Planning for quality Addressing Story points Discovering the Business value How to manage an Agile product throughout the Software Development Life Cycle The Creation and prioritizing of the Product Backlog Sizing and Estimation Looking at Effective team communication How to Monitor, progress and look at forecasting Reporting Scaling Agile Release Planning and Tracking
512 Scrum for Managers and Executives 7 hours This course is also know as SCRUM awareness training. Who should attend? This course has been created for managers, executives and other decision makers who want to know how to calculate the benefits of implementing the methodology or want to understand what their team is doing. It is also suitable for customers of software development wishing to have a stake holding in the development process. Short Overview of Project Management Methodologies and Frameworks Chaos Waterfall Prince2 Agile Why Agile? Comparison of iterative methodologies Why things go wrong The Agile approach What is Scrum? Pigs and chickens Product owner The customer representative Prioritizing product requirements Writing effective stories Acceptance criteria Negotiating sprint contents Group exercise to produce customer requirements and write stories based on the requirements The sprint Sprint backlog Sprint planning: what to do Sprint planning how to do it What happens during a sprint Burn down charts Group exercise to plan a sprint Scrum Master Implementing Scrum Ensuring proper practices Maintaining documentation Standup meetings When to pair program Group exercise to implement Scrum Finishing a sprint Scrum review meeting Scrum retrospective meeting Releasing an iteration Group exercise the review a sprint Is Agile and Scrum for you? Review of the Scrum process Comparison with other methodologies Benefits of pair programming Question and Answers Session
2629 Agile Project Management with Kanban 14 hours Target group: IT Director, Project Manager, Technical Team Leader, Analyst, Software Developer, Tester Learning objective: The purpose of this training is to acquire knowledge and practice of the workshops  aspects of Kanban and Agile foundations. Introduction to Agile Why Agile? What are the main objectives of Agile? How works mechanisms in Agile? How Agile can help? Command & Control vs. Agile Factory model The functioning of canon The functioning of missile Pillars of Kanban Big Picture Process Concepts behind Kanban Kanban Rules Metrics Flow Diagram + technical practices  Team work Shared responsibility Self-organization Interdisciplinary Benefit the "right" team work Kanban Board How to visualize process? How to create Kanban Board? What are and how to introduce WIP limits? What are and how to introduce Classes of Service? Customer Engagement The most common waste Value Stream Waste Value Stream Mapping Waste analysis Main concepts behind Kaizen (MUDA / MURI / MURA) Bottlenecks analysis Five Focusing Steps Simulation Simulation game Discussions Advanced topics
2644 The Scrum Test Specialist 7 hours This course is designed for testers, from a traditional test background, who are seeking to find their place in an Agile development environment. There is no specific Tester role in Scrum - there is just the Team. The Team collectively is responsible for the quality of the delivery, including testing, and so the ‘traditional’ Tester role is redundant. However, this course demonstrates how a Team member specialising in testing can add a great deal of value in the Scrum development process. Overview of Agile The Agile manifesto and principles Benefits of Agile Scrum overview and context Scrum Development Process Scrum components – 4 ceremonies, 4 artefacts, 3 roles The Scrum Process Comparison of V-Model to Agile Approach to Software Testing Traditional requirements v User Stories Valuing working software over documentation – what test documentation is needed? Conveyor belt v Collaboration – working in one Team The Contribution of the ‘Test Perspective’ to: The Sprint Review The Sprint Retrospective Backlog grooming and estimation The Test Specialist’s Tool Bag Exploratory testing Automated testing
2645 Building an Effective Scrum Team with Belbin Team Roles 7 hours The self-organising Scrum Team is the bedrock of the Scrum development process. An effective team is directly related to more effective delivery of products of value. Belbin Team Roles theory is used worldwide to help create more effective teams, in all kinds of environments. This course is led by a Belbin Accredited Trainer and Certified ScrumMaster. It provides a detailed overview of Scrum and examines how understanding Belbin Team Roles can benefit the Scrum Team. Scrum Overview The Agile manifesto and principles Scrum components – 4 ceremonies, 4 artefacts, 3 roles The Scrum Process Belbin Team Roles The 9 Belbin Team Roles Developing  your individual strengths for team success Understanding allowable weaknesses Understanding Team Roles in the Scrum Activities User Story grooming Backlog estimation Self-organising task allocation Review and retrospective meetings Team Dynamics Understanding how others affect your behaviour Handling difficult people How to deal with missing Team Roles
287825 Agile Software Testing with Continuous Integration 28 hours QA/CI What is QA? What is CI The costs of software development, refactoring and fix errors Identifying and understanding the project Profit for the organization DDD Software development based on business requirements, assumptions DDD Problems in communication IT-Business Domain Model Best Practices KISS principle and DRY Coding standards Creating reusable code through OOP and design patterns Identifying and reducing cyclomatic complexity Software Metrics Weight Method per Class Response For a Class Depth of Inheritance Tree Coupling Between Objects Lack of Cohesion of Methods Number of Children Cyclomatic complexity Metrics class Model Metrics Metrics for use Software Testing What, when and how to test? The method of "white-box" and "black box" The role of testing in agile methodologies TDD only a potential increase in the cost of the project Unit testing Behavioral tests Functional tests Refactoring What is refactoring? Debt technology Code smell Refactoring patterns Documentation The role of documentation in agile methodologies What to document? Types of documentation Documentation and agile methodologies, or you can call (Working software over comprehensive documentation)? Standard XMI Automatic generation of documentation Tools and Environment CI Tools and Environment CI Agile and CI/QA Planning and incremental development Embracing Change Short stages Interdisciplinary team Extreme Programming, Code Review Individuals and interactions over processes and tools Summation Discussion Questions How do you begin the process of implementation? Introduction to testing Functional Tests Regression Test UAT Tests Unit Tests Usability Tests Non Functional Tests Performance test Load test Stress test Soak test Test or not to test Who is making decisions about what to test? The cost of testing irrelevant things Calculating ROI (what if something fails analysis) The role of Test Manager The process of Testing Testing is a process and a strategy Identifying testing needs Gathering requirements (use cases, user stories) Scoping (choosing and prioritize scenarios) Designing tests Preparing data Preparing environment Creating or Recording tests Perform the test Analysis and reports Conclusions and improvement When to say "stop" Product owner and Tests The customer representative and test priority Prioritizing tests Writing effective stories for UAT Acceptance criteria Group exercise to produce customer requirements and write stories based on the requirements and create tests
300494 Scrum Essentials Workshop 14 hours This course is very much structered towards a workshop approach to enable delegates an opportunity to practise the Scrum and Agile skills. Day 1 Morning Agile principles & Scrum overview Day 1 Afternoon Release planning exercise – including definition of done, Product Backlog creation, prioritisation, estimation and refining Simulation Sprint 1 (all Sprints will include: Sprint Planning, creating/implementing Sprint Backlog, Review) Retrospective on Sprint 1 Day 2 Morning Backlog refining exercise – focus on estimation, story points and velocity Simulation Sprint 2 - focus on relationships with other stakeholders, burndown charts, Review meeting Retrospective on Sprint 2 Day 2 Afternoon Simulation Sprint 3 – focus on team dynamics Retrospective on Sprint 3 Simulation Sprint 4 Retrospective on Sprint 4
301002 An Introduction to the Scrum Team Role 7 hours This course is a comprehensive introduction to the world of Scrum for all those prospective members of the Scrum team (analysts, developers, testers et al) who want to be more effective as a Scrum member, but don’t particularly want to become a ScrumMaster or Product Owner. For those who do want to become a ScrumMaster, it also provides a good introduction to the Scrum Alliance Certified ScrumMaster syllabus. Overview of Agile Comparison of Agile to traditional methodologies The Agile manifesto and principles Benefits of Agile Scrum overview and context Scrum Development Process Scrum components – 4 ceremonies, 4 artefacts, 3 roles The Scrum Process User Stories Understanding User Stories Story grooming Effective Teamwork Self-organising team principles Techniques for developing more effective teamwork Estimation Estimating principles Estimating as a team with Planning Poker
2472 Managing Projects using Waterfall and Agile Techniques 14 hours This 2 day course is suitable for any IT professionals who are interested in using the Waterfall model and how people have traditionally tried to deal with its shortcomings - including, but not limited to, Agile approaches. The aim of the 1st day is to give an overview of these approaches enabling you to decide what might suit them in your environment. The 2nd day looks at project management techniques and good practices that have been identified from Agile, and which can be applied in a Waterfall or Agile context.Day 1 - Managing Software Projects in a Waterfall Context 1. Introduction to Waterfall a. Historical Context Winston Royce Background in manufacturing processes b. Waterfall stages Requirements gathering Design Implementation Verification Maintenance c. Waterfall challenges Handling change Distance between business knowledge and implementation Storing risk to late in the lifecycle Prioritisation of scope d. Summary of reactions to Waterfall model Embrace – Waterfall approaches, eg SSADM Cope – V-Model Adapt – Incremental Reject – Agile Enhance – Lean 2. V-Model coping strategies for Waterfall delivery a. Early verification and validation Cost of finding late Reviews and inspections Static analysis b. V-Model test stages Unit/Unit integration System System Integration Acceptance c. V-Model benefits Increased end-user involvement in verification Early risk mitigation 3. Adapting Waterfall with Incremental approaches a. Types of Incremental approaches Pre-planned  Parallel, RAD Evolutionary, RUP b. Incremental delivery principles Product increments Proto-typing Timeboxing c. Benefits of incremental delivery Increased user involvement in decision making Early return on investment Reacts to change  4. Rejecting the Waterfall model in favour of Agile a. Agile Essentials Agile Manifesto Agile Principles b. Introduction to Scrum, the most popular Agile framework Iterative delivery Collaborative working Just in time documentation Adaptive planning c. Benefits of Agile Increased user involvement throughout process Empowered development team Rapid return on investment Greater ability to react to change Reduce nugatory development 5. Enhancing Waterfall with Kanban delivery a. Lean and Kanban  History of Lean delivery  History of Kanban Principle of reducing waste b. Introduction to Kanban The Kanban board Managing work-in-progress c. Benefits of Kanban Greater ability to react to change Rapid return on investment Reduce nugatory development Day 2 - Agile Project Management Techniques 1. Empirical Process Control a. Inspect Demonstration Retrospection b. Adapt Adaptive planning Continuous improvement c. Transparency Stakeholder involvement Contract negotiation Just in time documentation 2. Managing requirements a. Backlogs Product Release Sprint b. Backlog Items User Stories Defects Requirements specifications c. Risk Adjusting Backlog for risk Risk burndown 3. Estimation and control a. Timebox planning Release planning Iteration planning Daily communication b. Prioritisation techniques MoSCow Value based Other techniques c. Estimation techniques User story grooming Planning Poker 4. Delivery management a. Iterative delivery Team velocity Rapid return on investment b. Information radiators Scrum wall Burn-down chart 5. Team management a. Associative leadership ScrumMaster as facilitator Role of the traditional project manager b. End-user involvement The single decision maker - the Product Owner Communicating with stakeholders (Pigs and Chickens) c. Empowered team Self-managing teams The role of the specialist within the team Managing split teams
1952 Agile Software Testing 14 hours This course has been created for test managers, quality assurance staff, testers, software developers, project managers and management in order to explain how the Agile project management frameworks (notably SCRUM) deal with testing. At the end of the course, each of the delegates will design and execute a test plan for a sample application (it can be an actual client application if available) Where the requirements come from? Traditional Business Analysis Use Cases, Scenarios and Tests Non functional requirements Performance Conformance UML in Business Analysis Introduction to testing Functional Tests Regression Test UAT Tests Unit Tests Usability Tests Non Functional Tests Performance test Load test Stress test Soak test Test or not to test Who is making decisions about what to test? The cost of testing irrelevant things Calculating ROI (what if something fails analysis) The role of Test Manager The process of Testing Testing is a process and a strategy Identifying testing needs Gathering requirements (use cases, user stories) Scoping (choosing and prioritize scenarios) Designing tests Preparing data Preparing environment Creating or Recording tests Perform the test Analysis and reports Conclusions and improvement When to say "stop" Product owner and Tests The customer representative and test priority Prioritizing tests Writing effective stories for UAT Acceptance criteria Group exercise to produce customer requirements and write stories based on the requirements and create tests The sprint Sprint backlog and tests user stories Group exercise to plan a sprint Finishing a sprint Scrum review meeting is a test Is Agile and Scrum for you? Review of the Scrum process Comparison with other methodologies Benefits of pair programming Question and Answers Session
300774 Analyse Efficace des Exigences avec les Méthodes Agiles et une Modélisation Agile 21 hours Objectif: Aider la Maîtrise d'Ouvrage (MOA) et l'assistance MOA à comprendre comment réussir une analyse efficace des exigences en partant de leur vision métier et cahier des charges, tester les exigences et guider les développeurs précisement dans leur implémentation. Cette formation de trois jours a pour objectif d'aider les participants de la MOA à spécifier leurs besoins à partir de la vision métier et de découvrir les cas d'utilisation et user stories appropriés de leur système d'information en structurant ces besoins. En dernière étape, les participants y apprennent à passer à la description détaillée de leurs scénarios de cas d'utilisation et de user stories afin de les faire valider par les utilisateurs et préparer les tests de recette. Ainsi, en utilisant une modélisation UML agile appropriée au langage des analystes, cette formation leur permet de structurer leurs exigences afin de les communiquer efficacement aux analystes et concepteurs de la MOe au travers d'une démarche de recueil incrémental. Introduction Présentation de l'activité du Recueil des Besoins et des Exigences au sein d'un projet Les fondements d'une livraison agile du logiciel Les 5 niveaux d'un management de projet agile Positionnement au sein des méthodes agiles Scrum et DAD ainsi que le Processus Unifié (RUP) Les Rôles, l'équipe et environnements Un panorama des diagrammes UML pour modéliser les besoins et les exigences Cadre Méthodologique pour la traçabilité des exigences vers leur implémentation et les tests Etude de Cas : Recueil des Besoins et des Exigences dans un processus itératif Description des exigences utilisateurs par le modèle des cas d'utilisation agiles et des user stories Gestion du product backlog : Qualification des exigences (le modèle Kano) Les fondements du diagramme de cas d'utilisation : périmètre fonctionnel du système, acteurs, cas d'utilisation, user stories Identification des cas d'utilisation sur la base des exigences utilisateurs Estimation Agile et Planning Etude de Cas : Découverte des cas d'utilisation et des user stories en partant d'un cahier des charges (product backlog) et des besoins utilisateurs Description de la Vision et des besoins métier par le modèle des cas d'utilisation Cas d'utilisation métier issus de la vision et des exigences métier Description des cas d'utilisation métier avec des diagrammes d'activité de processus Passerelle vers les cas d'utilisation système en partant de la vision et des exigences métier Découverte des scénarios de cas d'utilisation et des user stories Etude de Cas : Identifier les cas d'utilisation et user stories sur la base de la vision métier Validation et test des spécifications Le processus incrémental de recueil des exigences et le sprint backlog Des règles pour une description efficace de cas d'utilisation, user stories et éléments d'architectures Diagrammes pour valider les cas d'utilisation et user stories Comment choisir le diagramme approprié ? Raffinement des fonctions Scrum avec les cas d'utilisation et leurs relations Comment tester les exigences avec le modèle Test-Driven Requirements ? Contrats d'Opérations pour guider les dévéloppeurs dans l'implementation des exigences Etude de Cas : Valider, tester les exigences et les communiquer aux dévéloppeurs Conclusion Etapes du recueil des besoins, des exigences et de l'analyse système Traçabilité entre les exigences et les modèles d'analyse Patrons pour le recueil et le test des exigences Note: Afin de servir de support à la traçabilité entre les exigences et les spécifications détaillées, les sessions ci-dessus se déroulent en compagnie d'outils d'Ingénierie des Besoins et de Modélisation UML et SysML tels queEA (Enterprise Architect). Les concepts et livrables sont d'abord expliqués sur des cas simples et ensuite appliqués à vos propres besoins. Des sessions de revues peuvent être également planifiées selon besoin. Fourni par GooBiz

Les Formations à Venir

Weekend Scrum cours, Soir Scrum formation, Scrum stage d’entraînement, Scrum formateur à distance, Scrum formateur en ligne, Scrum formateur Online, Scrum cours en ligne, Scrum cours à distance, Scrum professeur à distance, Scrum visioconférence, Scrum stage d’entraînement intensif, Scrum formation accélérée, Scrum formation intensive, Formation inter Scrum, Formation intra Scrum, Scrum formateur, Scrum cours particulier, Scrum formations privées,Weekend Scrum formation, Scrum instructeur, Scrum préparation, Scrum sur place, Soir Scrum cours, Scrum coaching, Scrum cours, Scrum entraînement, Scrum professeur, Scrum stage de formation, Scrum cours particuliers

Nos clients