Professional Scrum Developer™ Neno Loje - Your Agile Facilitator

Professional Scrum Developer™ (.NET)-Kursinhalte

Informationen zu Inhalten, Zielen und Agenda (in englischer Sprache)

Hinweis zur Kurssprache: Der Kurs wird komplett auf Deutsch gehalten; die lizenzierten Kursunterlagen und Präsentationsfolien von sind auf Englisch verfasst.

Course Description’s Professional Scrum Developer course is a unique and intensive three-day experience intended for anyone involved in software development. The course guides teams on how to turn product requirements into business value in the form of potentially- releasable increments of software. This is done using the Scrum framework, Visual Studio 2013, and modern Agile development practices.

This course is a mix of lecture, demonstration, group discussion, and hands-on software development. The true value of the course is realized as each student collaborates with other team members, on a case study product, using a shared instance of Microsoft Team Foundation Server 2013, over several mini-Sprints.

Day 1   Day 2
  • Scrumdamentals
  • Scrum Simulation
  • Application Lifecycle Management
  • Agile Testing
  • SPRINT 2
  • Case Study
  • Refining and Estimating
  • SPRINT 1
  • Emergent Architecture
  • SPRINT 3
Day 3    
  • Quality Code
  • SPRINT 4
  • Scrum Challenges
  • Next Steps

The Sprints

Timeboxing is a critical concept in Scrum as well as in this course. This is especially evident during the Sprints. Each event within a Sprint has a timebox duration and each team is expected to obey it.

Component Description Minutes
Sprint Planning The Product Owner presents an ordered Product Backlog and the Development Team forecasts and plans its Sprint Backlog 15
Development The Development Team self-organizes to complete their plan, develop the PBIs, and deliver a done increment of functionality 75
Refining The Scrum Team inspects and adapts the Product Backlog during Sprint
Sprint Review Each team presents their done increment for feedback 15
Sprint Retrospective A group retrospective meeting is held to inspect and adapt the current Sprint in hopes of making the next Sprint more effective 15


This course is suitable for any member of a Scrum Development Team, such as those who develop tests, architecture, design, schema, or code. Entire teams are encouraged to attend this course and experience the positive effects of collaborating inside of a timebox according to their definition of done. Each team must be cross-functional, ensuring it has the necessary skills. Product Owners, Scrum Masters, stakeholders, and those evaluating Scrum’s effectiveness are welcome to attend, but keep in mind that every attendee will be expected to participate and collaborate equally, working towards the achievement of their team’s goals.

Note: This course assumes that each student has read the Scrum Guide, has a basic understanding of Scrum, and is using Visual Studio 2013 Premium edition (or above). Failure to meet any of these prerequisites may result in a diminished learning experience.

At Course Completion

Through a combination of certified instructor-led training, hands-on activities, and team exercises you will be exposed to the key components of Scrum and the skills required to help successfully develop software using Visual Studio. At course completion, attendees will have had exposure to most of the topic areas outlined in the Professional Scrum Developer Objective Domain:

Fundamentals of the Scrum framework
  • Scrum roles, artifacts, and events
  • Complementary development practices
Application Lifecycle Management
  • Visual Studio ALM Tools
  • Visual Studio Scrum process template
  • Team Web Access Agile planning tools
  • Team Foundation Version Control
  • Branching and merging for Scrum Teams
  • Support for various release models
Refining the Product Backlog
  • Defining and assuring quality
  • Definition of done
  • Reporting bugs
  • In-Sprint vs. out-of-sprint bugs
  • INVEST and 3C techniques
  • Agile estimation
  • Wall estimation and Planning Poker techniques
Agile Testing
  • Testing in parallel with coding
  • Development, acceptance, and exploratory testing
  • Unit testing in Visual Studio
  • Test-Driven Development
  • Analyzing code coverage
  • Acceptance testing in Visual Studio
  • Microsoft Test Manager
  • Acceptance Test-Driven Development
Emergent Architecture
  • Fitness (fit) for purpose
  • Avoiding upfront requirements and design
  • Developing in slices, not layers
  • Minimizing documentation
Quality Code
  • Quality code == quality software
  • SOLID principles
  • Clean code == quality code
  • Code and test smells
  • Code quality support in Visual Studio
  • Code Analysis, Code Metrics, Code Clone Analysis
  • Continuous Integration (CI)
  • Automating builds with Team Foundation Build
  • CI support in Team Foundation Build
  • Continuous feedback and related tools
  • Refactoring and refactoring tools
  • Technical debt and how to pay it back
Scrum Challenges
  • Getting done and avoiding undone work
  • Renegotiating scope
  • Running experiments (spikes)
  • Cross-functional team collaboration
  • Not changing Scrum
  • Overcoming common dysfunctions & case studies
  • Working with challenging team members
  • Improving productivity
  • Becoming a high-performance Scrum Team

Course Designer

This course was designed by Richard Hundhausen, a Visual Studio ALM MVP, Microsoft Regional Director, and author of Professional Scrum Development with Microsoft Visual Studio 2012 (Microsoft Press). For more information about his company, or to see other courses that they offer, visit

Each team is expected to self‐organize and manage their own work during the sprint. Pairing is highly encouraged. The instructor/product owner will be available if there are questions or impediments, but will be hands‐off by default. You should be prepared to communicate and work with your team members in order to achieve your sprint goal. If you have development‐related questions or get stuck, your partner or team should be your first level of support.



This is a unique course in that it’s technically‐focused, team‐based, and employs timeboxes. It demands that the members of the teams self‐organize and self‐manage their own work to collaboratively develop increments of software.

All students must commit to:

  • Pay attention to all lectures and demonstrations
  • Participate in team and group discussions
  • Work collaboratively with other team members
  • Obey the timebox for each activity
  • Commit to work and do your best to deliver

All students should have:

  • An understanding of Scrum
  • Familiarity with Visual Studio (2012 or 2013)
  • C# & .NET (4.0 and higher) experience*
  • Software testing experience

* Check with instructor for the exact technologies that will be in use.

People who should not take this course include:

  • Students requiring command and control style instruction (there are no prescriptive/step‐by‐step labs in this course)
  • Students who are unwilling to work within a timebox
  • Students who are unwilling to work collaboratively on a team
  • Students who don’t have any skill in any of the software development disciplines
  • Students who are unable to commit fully to their team (not only will this diminish the student’s learning experience, but it will also impact their team’s learning experience)

» Zurück zur Kursbeschreibung