Professional Scrum Developer.Net Certification - Kuala Lumpur

Organiser
Flipside Sdn Bhd
Date
11-13 Aug 2012 (Add to calendar) GMT
Venue
Eastin Hotel , Petaling Jaya, MY
Cost
RM 4150

Module 1 – Introduction This module provides a chance for the attendees to get to know the instructors as well as each other. The PSD programme, as well as the day by day agenda, will be explained. Finally, the Scrum team will be selected and assembled so that the forming, storming, norming, and performing can begin.

• Trainer and student introductions • Professional Scrum Developer programme • Agenda • Logistics • Team formation • Retrospective

Module 2 – Scrum Fundamentals This module provides a level-setting understanding of the Scrum framework including the roles, events, and artifacts. The team will then experience Scrum first-hand by simulating a multi-day sprint of product development, including planning, review, and retrospective meetings.

• Scrum overview • Scrum roles • Scrum events (timeboxes) • Scrum artifacts • Simulation • Retrospective

Note : It’s required that you read Ken Schwaber’s Scrum Guide in preparation for this module and course.

Module 3 – Implementing Scrum in Visual Studio 2010 This module demonstrates how to implement Scrum in Visual Studio 2010 and Team Foundation Server 2010. The team will learn the mapping between the Scrum concepts and how they are implemented in the tool. After connecting to the shared Team Foundation Server, the team members will then return to the simulation, this time using Visual Studio to manage their product development.

• Mapping Scrum to Visual Studio 2010 • Product Backlog/User Story work items • Task work items • Bug work items • Test Case work items • Queries and Reports • Demonstration • Simulation • Retrospective

Module 4 – The Case Study In this module, the team is introduced to their problem domain for the week. A kick-off meeting by the Product Owner (the instructor) will set the stage for the why and what that will take during the upcoming sprints. The team will then define the quality attributes of the project and their definition of “done.”

The legacy application code will be downloaded, built, and explored, so that any bugs can be discovered and reported.

• Introduction to the case study • Download the source code, build, and explore the application • Define the quality attributes for the project • Define “done” • How to file effective bugs in Visual Studio 2010 • Retrospective

Module 5 – Hotfix This module drops the team directly into a Brownfield (legacy) experience by forcing them to analyze the existing application’s architecture and code in order to locate and fix the Product Owner’s high-priority bugs. The team will learn best practices around finding, testing, fixing, validating, and closing a bug.

• How to use Architecture Explorer to visualize and explore • Create a unit test to validate the existence of a bug • Find and fix the bug • Validate and close the bug • Retrospective

Module 6 – Planning This short module introduces the team to release and sprint planning within Visual Studio 2010. The team will define and capture their goals as well as other important planning information.

• Release vs. Sprint planning • Release planning and the Product Backlog • Product Backlog prioritisation • Acceptance criteria and tests • Sprint planning and the Sprint Backlog • Creating and linking Sprint tasks • Retrospective.

At this point the team will have the knowledge of Scrum, Visual Studio 2010, and the case study application to begin developing increments of potentially shippable functionality that meet their definition of done.

Module 7 – Emergent Architecture This module introduces the architectural practices and tools a team can use to develop a valid design on which to develop new functionality. The teams will learn how Scrum supports good architecture and design practices.

After the discussion, the teams will be presented with the product owner’s prioritised backlog so that they may select and commit to the functionality they can deliver in this sprint.

• Architecture and Scrum • Emergent architecture • Principles, patterns, and practices • Visual Studio 2010 modeling tools • UML and layer diagrams • SPRINT 1 • Retrospective

Module 8 – Test Driven Development This module introduces Test Driven Development as a design tool and how to implement it using Visual Studio 2010. To maximise productivity and quality, a Scrum team should setup Continuous Integration to regularly build every team member’s code changes and run regression tests. Refactoring will also be defined and demonstrated in combination with Visual Studio’s Test Impact Analysis to efficiently re-run just those tests which were impacted by refactoring.

• Continuous integration • Team Foundation Build • Test Driven Development (TDD) • Refactoring • Test Impact Analysis • SPRINT 2 • Retrospective

Module 9 – Agile Database Development This module lets the SQL Server database developers in on a little secret – they can be agile too. By using the database projects in Visual Studio 2010, the database developers can join the rest of the team. The students will see how to apply Agile database techniques within Visual Studio to support the SQL Server 2005/2008/2008R2 development lifecycle.

• Agile database development • Visual Studio database projects • Importing schema and scripts • Building and deploying • Generating data • Unit testing • SPRINT 3 • Retrospective

Module 10 – Ship It Teams need to know that just because they like the functionality doesn’t mean the Product Owner will. This module revisits acceptance criteria as it pertains to acceptance testing. By refining acceptance criteria into manual test steps, team members can execute the tests, recording the results and reporting bugs in a number of ways.

Manual tests will be defined and executed using the Microsoft Test Manager tool. As the Sprint completes and an increment of functionality is delivered, the team will also learn why and when they should create a branch of the codeline.

• Acceptance criteria • Acceptance testing in Visual Studio 2010 • Microsoft Test Manager • Writing and running manual tests • Branching • SPRINT 4 • Retrospective

Module 11- Overcoming Dysfunction This module introduces the many types of people, process, and tool dysfunctions that teams face in the real world. Many dysfunctions and scenarios will be identified, along with ideas and discussion for how a team might mitigate them. This module will enable you and your team to move toward independence and improve your game of Scrum when you depart class.

• Scrum-butts and flaccid Scrum • Best practices working as a team • Team challenges • Scrum Master challenges • Product Owner challenges • Stakeholder challenges • Course Retrospective

Scrum FAQ (Optional) Time permitting, the instructor will present a list of frequently asked questions about Scrum, implementing Scrum, and the PSD programme. The instructor may either lead a discussion around these topics or use this section as reference.

• Scrum FAQs • Professional Scrum Developer FAQs

Scrum Assessment (Optional) Time and environment permitting, the instructor may give the students time during class to take the respective Scrum.org Assessment so that the students can leave class potentially certified!

The Sprints

You might also like...

Comments

Other nearby events

Map

Contribute

Why not write for us? Or you could submit an event or a user group in your area. Alternatively just tell us what you think!

Our tools

We've got automatic conversion tools to convert C# to VB.NET, VB.NET to C#. Also you can compress javascript and compress css and generate sql connection strings.

“The difference between theory and practice is smaller in theory than in practice.”