As the only official training for users of Team Foundation Server (TFS) and Visual Studio Team Services (VSTS) you will learn how to apply modern, agile engineering practices in Scrum to increase your software delivery capabilities. This course focuses on the Development Team and teaches them how to build high quality software in 30 days or less.
Once your organisation has mastered the foundations of Scrum you can focus on the engineering practices that allow you to build software and prepare for DevOps as a professional team. You cant focus on delivering faster with DevOps at scale until you have a professional Scrum team. Scale or speed is much less likely to succeed with an amateur team.
Take your Scrum Development Team and turn them into professionals with practical experience’s of refinement, planning, source control, emergent architecture, test driven development, and Build automation using Visual Studio Team Services. In conjunction with various technology stacks you will learn how to test, build, and refactor your code to improve quality and deliver business value.
Why Martin Hinshelwood & naked Agility
Martin Hinshelwood is a Professional Scrum Trainer who provides training and consulting on both DevOps and Agility for organisations all over the world.
Martin has been certified by Scrum.org who provide the highest quality Scrum training in the world. Our training material is created and maintained by Scrum co-creator Ken Schwaber, and the community of Professional Scrum Trainers worldwide. This is the most up-to-date material with the software industry, its trends, and the latest software practices.
Martin Hinshelwood brings his own style and stories, born from his experience consulting from Seattle to Charlotte, Glasgow to Oslo, and Pune to Beijing. He comes highly recommended by previous students around the world.
Learn more than you ever have before
Students are challenged to implement and apply modern engineering standards and technical excellence within Scrum. They take home an increased understanding of how to collaborate better as a team.
- Students will have a clear understanding of the mechanics of Scrum and their cohesion.
- Students will learn what engineering practices to adopt to increase the effectiveness of Scrum.
- Students leave the class with a handful of tips to identify common impediments and dysfunctions.
- Students can be more effective in a Scrum Development Team.
- The Scrum Framework
- Application Lifecycle Management
- Working from the Product Backlog
- Agile Testing
- Emergent Architecture
- Quality Code
- Scrum Challenges
This course is for you if…
The Professional Scrum Developer course is suitable for any member of a Development Team, including architects, programmers, database developers, testers, business analysts, designers, and others with some technical knowledge. This is a technical class and, as such students may need to pair with others on their team at times.
Before coming to the course
Attendees make the most of the class if they:
Assessment and certification
The Professional Scrum Development Team course has the Professional Scrum Developer level I (PSD I) as its associated credential. All participants completing the Professional Scrum Development Team course receive a password to take the PSD I assessment.
This industry-recognized certification requires a minimum passing score on the associated rigorous assessment. Scrum.org maintains a public list with everyone holding a PSD I credential.
Students work in teams. They learn self-organization through collaboration, conversation, and hands-on exercises.
Related Posts from Martin Hinshelwood
Check out our latest posts and see what we have been working on.
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.
The Product Owner presents an ordered Product Backlog and the Development Team forecasts and plans its Sprint Backlog
The Development Team self-organizes to complete their plan, develop the PBIs, and deliver a done increment of functionality
The Scrum Team inspects and grooms the Product Backlog
Each team presents their done increment for feedback
A group retrospective meeting is held to inspect and adapt the current Sprint in hopes of making the next Sprint more effective
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
- Automating builds with Team Foundation Build
- Support for various release model
- Product Backlog Grooming
- 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
- 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
- Fitness (fit) for purpose
- Avoiding upfront requirements and design
- Developing in slices, not layers
- Minimizing documentation
- 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)
- CI support in Team Foundation Build
- Continuous feedback and related tools
- Refactoring and refactoring tools
- Technical debt and how to pay it back
- 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