Scrum Schulungen

Scrum Schulungen

Scrum Project Management courses

Scrum Schulungsübersicht

ID Name Dauer Übersicht
359679 Efficient Requirement Management using Agile Methods and Agile UML Modeling 21 hours Objective: This training course aims at helping product managers, products owners, business analysts, system architects and developers understand how to efficiently Manage Requirements on the basis of the product vision till guiding developers accurately in implementing them. More in detail, this course aims at assisting product managers in better defining the value propositions of their products on the basis of strategies and stakeholder needs. Business Analysts and product owners understand how to describe requirements of the product backlog then discover appropriate epics and user stories of the system while contributing to the required value creation. Along interactive case study exercises, participants learn how to describe in detail such requirements in order to validate correct understanding of needs and prepare system acceptance tests. Thus, only using a very common and productive UML profile, they learn to structure requirements in order to communicate efficiently with architects and developers through an iterative requirement gathering process. Audience: Product Managers Product Owners Business Analysts Anyone interetsted in the Requirements Management Process Introduction What is the Requirement Management Process ? Why Agile ? Business agility and agile software delivery : Definitions Linking Agile to Business : Business Motivation Model vs. Business Model Canvas, How to effciently use the Value Proposition Canvas for defining the Product Vision ? Business agility vs. agile software delivery principles What is Agile Not ? Impacts of alignment with strategies and capabilities Requirement Management in an Agile Context Scrum Life Cycle : Issues about completeness of requirements and traceability How productive models enhance communication in 'Agile' ? Business Extensions of Agile : Structuring Business Value Contribution of a User Story A Panorama of UML diagrams for modeling requirements Frameworks for tracing requirements toward software implementation and tests The 5 levels planning of an agile project (from Clarifying the Vision and Product Backlog to Tasks… and the Architecture Walking Skeleton) Managing Requirements within Agile Methods (Scrum, DAD) vs. the Unified Process (RUP) Roles, teams, environments Presentation of the Case Study for Structuring requirements and managing them using an iterative process How to describe the business vision and needs via traceable models ? Qualification of the requirements : The Kano model vs. the Value Proposition Canvas Structuring the Vision of the Product on the basis of strategies, environmental forces and trends Value proposition, key activities, key resources, revenue streams and cost structures,  Discovering the business scope of the product using the customer needs, gains and pains Describing business use cases using 'value streams' and 'value stages' Bridging the business scope of the product with expected 'value contributions' Case Study : Describing the vision of the product How to describe user needs via agile use case modeling (epics and user stories) ?  Agile Estimating and Planning Building and managing the product backlog / granularity of requirements Ahead of the sprint planning Creation of the sprint backlog Agile User Story Pattern : system scope (the subject), actors, use cases, user stories, acceptance criteria, the INVEST model The Walking Skeleton using Disciplined Agile Delivery : From Processes to Technology  How to find out epics and user stories on the basis of value streams ? Value contribution of epics and user stories Writing tasks : granularity and size using the SMART model Case Study : Discovering epics and user stories on the basis of value streams Validating and testing correct understanding of detailed specifications  Using an incremental requirement gathering process and the sprint backlog Rules for efficient epic, user story and architecture descriptions Diagrams for validating epics and user story descriptions  How to choose the right diagram ?  Refining features using use cases and relationships modeling Testing correct understanding of requirements using Test-Driven Requirements Given/When/Then structures and Operation Contracts for guiding developers in implementing requirements Coverage analysis and change management Case Study : Validating, testing and communicating detailed requirements to developers Conclusion Steps of efficient requirement gathering and system analysis processes  Traceability between requirements and analysis models  Patterns for gathering and testing requirements  Notice: The above training-mentoring sessions are conducted interactively using examples from Requirement Engineering and Modeling tools in order to ensure good level of traceability between requirements and underlying solutions. Concepts are first explained using basic examples and are then followed by solution drafts to your potential case. After this session, we can also accompany you by reviewing and validating your solutions depending on your needs.
566902 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
234928 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
25199 Agile Projekt Management mit Kanban 14 hours Target group: IT Director, Project Manager, Technical Team Leader, Analyst, Software Developer, Tester Learning objective: The purpose of training is to acquire knowledge and practice at 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
123885 Der Scrum Test-Spezialist 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
124006 Entwicklung eines effektiven Scrum-Teams mit Teamrollen nach Belbin 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
124024 Eine Einführung in die Scrum Team Role 7 hours Dieser Kurs ist eine umfangreiche Einführung in die Welt des Scrum für alle angehenden Mitglieder des Scrum-Teams (Analytiker, Entwickler, Tester etc), die ihre Effektivität als Scrum-Mitglied steigern, aber weder Scrum-Master noch Product-Owner werden möchten.  Für diejenigen, die ScrumMaster werden möchten, gibt es auch eine gute Einführung in den Scrum Alliance Certified ScrumMaster syllabus Überblick agiler Vorgehensweisen Vergleich agiler zu traditionellen Vorgehensweisen Das agile Manifest und Prinzipien Vorteile von agilen Vorgehensweisen Scrum Überblick und Zusammenhang Scrum Entwicklungsprozess Scrum Komponenten – 5 Aktivitäten, 4 Artefakte, 3 Rollen The Scrum Prozess User Stories Was sind User Stories? Story grooming Effektive Teamarbeit Prinzipien der Selbstorganisation Techniken für effektivere Teamarbeit Aufwandschätzung Prinzipien der Aufwandschätzung  Aufwandschätzung durch das Team mittels Planning Poker
24878 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
24880 Scrum für Manager und Führungskräfte 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
24983 Agiles Projektmanagement mit Scrum 14 hours Dieser zweitägige Kurs ist für IT-Profis geeignet, die eine iterative Methodologie wie Agile und Scrum in die Praxis umsetzen möchten. Der Inhalt spricht die Bedürfnisse von Projektmanagern, Teamkoordinatoren, Softwareentwicklern und Kunden an. Damit werden allen beteiligten Wege aufgezeigt, sich in den Entwicklungsprozess sinnvoll einzubringen. Warum Agile? Warum IT-Projekte scheitern Der Agile Weg Was ist Scrum? Vergleich iterativer Methodologien Die Fabel vom Schwein und dem Huhn Der Product Owner Repräsentant des Kunden Priorisieren von Anforderungen Schreiben von effektiven User Stories Akzeptanzkriterien Aushandeln der Inhalte eines Sprints Übung: Anforderungen herausfinden und daraus User Stories entwickeln Der Sprint Das Sprint Backlog Planung von Sprints: Was ist zu tun? Planung von Sprints: Wie wird es getan? Was passiert während eines Sprints? Burndown Graphen Übung: Einen Sprint planen Der Scrum Master den Scrum Prozess implementieren Hochwertige Praktiken sicherstellen Retrospektiven durchführen Dokumentation des Prozesses pflegen Übung: den Scrum Prozess umsetzen Das Scrum Team Das Sprint Backlog pflegen Standup Meetings abhalten die "Definition of Done" Wann ist Pair Programming sinnvoll? Das Ende eines Sprints Eine Iteration veröffentlichen Das Sprint Review Meeting Die Retrospektive Übung: Einen Sprint auswerten Sind Agile und Scrum für Sie geeignet? Stärken und Schwächen des Scrum Prozesses Vergleich mit anderen Methodologien Bekannte Hürden und Lösungsansätze Diskussion: Welche Aspekte von Agile können die Teilnehmer bei sich umsetzen?
148151 Scrum - Schritt für Schritt 14 hours Scrum ist die derzeit beliebteste agile Methode zur Prozessoptimierung in der Softwareentwicklung. Das Ziel des Kurses ist die Teilnehmer Schritt für Schritt mit Scrum vertraut zu machen. Dieser Kurs ist gleichermassen für Anfänger und Fortgeschrittene geeignet. Im Laufe des Kurses wird der Stoff des Zertifikats Professional Scrum Master I (http://www.scrum.org/psmoverview). Jeder Teilnehmer erhält die Gelegenheit sich mit dem Format der Zertifizierungsprüfung während einer Probeprüfung vertraut zu machen. Der Kurs besteht aus Theorie, Diskussion und praktischen Übungen. Agile Methoden der traditionelle Ansatz - Waterfall Lean Management Das Agile Manifest Scrum Die Geschichte von Scrum Schweine und Hühner Inspektion, Adaptierung und Transparenz Die Rolle des Scrum Masters Die Rolle des Product Owners Return of Investment - ROI Total Cost of Ownership - TCO Die Rolle des Scrum Teams Selbstorganisation Technische Verschuldung (technical debt) Testgesteuerte Entwicklung (TDD) Sprints Treffen in Scrum Daily Scrum Sprint Planung Sprint Review Retrospektive Das Product Backlog Schreiben von User Stories Schätzen Planning Poker und Story Points Das Sprint Backlog Burndown charts Definition of Done Praktische Übungen Selbstorganisation Erstellen eines Product Backlogs Inspektions- und Adaptionsschleife Schätzen in der Gruppe - Planning Poker Probezertifizierung
359635 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
24981 Agile Methoden zum Testen von Software 14 hours Dieser Kurs eignet sich für Test Manager, QA Personal, Tester, programmierer und Manager, die Softwaretests in einer agilen Umgebung (insbesondere SCRUM) kennen lernen möchten. Am Ende des Kurses wird jeder Teilnehmer einen Testplan für eine Beispielanwendung entwickeln und ausführen. Dies kann eine eigenes Softwareprojekt sein. Woher kommen die Anforderungen? Traditionelle Business Analyse Anwendungsfälle, Szenarios und Tests Nicht funktionelle Anforderungen Performance Konformität UML in der Anforderungsentwicklung Einführung ins Testen von Software Funktionelle Tests Regressionstests User Acceptance Tests Unit Tests Usability Tests Nicht funktionelle Tests Leistungstests Belastungstests Soak Tests Testen oder nicht testen Wer entscheidet, was getestet werden soll Der Preis für das Testen irrelevanter Dinge ROI Berechnung und Risikoanalyse Die Rolle des Testmanagers Der Prozess des Testens Testen ist ein Prozess und eine Strategie Testbedarf feststellen Anforderungen sammeln (Use Cases, User Stories) Szenarien auswählen und priorisieren Tests designen Testdaten vorbereiten Testumgebung vorbereiten Test erstellen oder aufnehmen Test ausführen Analyse und Bericht Schlussfolgerungen und Verbesserung Wann sollte man "STOP" sagen? Product Owner und Tests Repräsentant des Kunden Prioritisieren von User Stories und damit Tests Effektive Stories für User Acceptance Testing Akzeptanzkriterien Übung: Kundenanforderungen ermitteln, daraus User Stories und Tests entwickeln Der Sprint Sprint Backlog und Tests für User Stories Definition of Done Gruppenübung, um einen Sprint zu planen Den Sprint abschliessen Das Scrum Review Meeting ist ein Test Ist Agile/Scrum für Sie geeignet? Überblick über den Scrum Prozess Vergleich mit anderen Methodologien Fragen und Antworten
359692 Introduction to Scrum 14 hours Introduction to Scrum What is Agile? What is SCRUM? Why SCRUM?  Challenges 2 Artifacts / 3 Roles / 4 Events Case Study Online references / Study Material Scrum Ceritification Guidelines  

Upcoming Courses

CourseSchulungsdatumKurspreis (Fernkurs/Schulungsraum)
Agile Software Testing - BernMo, 2016-07-25 09:302090EUR / 2590EUR
The Scrum Test Specialist - BaselSa, 2016-08-06 09:30990EUR / 1230EUR
Agile Project Management with Kanban - ZürichMo, 2016-08-08 09:301850EUR / 2350EUR
Scrum Schulung, Scrum boot camp, Scrum Abendkurse, Scrum Wochenendkurse , Scrum Training, Scrum Seminar, Scrum Privatkurs, Scrum Lehrer , Scrum Coaching, Scrum Seminare

EINIGE UNSERER KUNDEN