The workshop that participants on average rate 8/10!

Nowadays Scrum and agile has become well known and mainstream. Most people that try it out are very happy with the results. Also, there are several studies that show that agile projects do on average 35% better than traditionally run projects.

We at Cedur have been using agile work methods since 1999 and are really happy about at the situation today. All our trainers/coaches have more than fifteen yeas of experience as software developers and extensive experience of agile work methods and change work.

In this class/workshop we try to offer something more than traditional Scrum training and pass on our experiences of what really works. The most successful agile companies do may times better than the average agile company and we focus on how this is possible and offers a guide on how to move in that direction.

This course is suitable for anyone that in some way is involved with developing software:

• Developers
• Project managers and line managers
• Customers or product owners

This course is designed as an active learning experience. It does include plenty of lecture-type sessions providing the latest knowledge in all the covered areas, but participants will also spend a fair share of the time talking, moving and doing exercises. The idea behind this is that things understood and learned through experience tend to stick much better.

 

Below is an outline of the standard delivery of this course. If you have requests for other/additional topics for your team, just let us know. We

will be happy to modify this to fit your needs.

 

Principles and values

• Software crisis, what is the problem with traditional methods?
• The Agile Manifesto. Uncovering better ways of developing software.
• Improvements, what is possible?
• Scrum background, roles, responsibilities, why it works
• Exercises: Self organizing teams and system boundaries, communicating requirements

What makes a great team

• Teamwork is an individual skill
• Responsibility Process Model
• The 5 dysfunctions of a team
• Need for productive conflict
• Feedback
• Conflict Management
• Team rules
• Workspaces
• Exercises: Responsibility Process model, Team skills

Lean Software Development

• Why Toyota consistently is 4 times more productive and has 12 timer higher quality than western car manufacturers
• Principles of Lean Software Development
• Identifying Waste
• Exercises: Batches and flow

Strategies for getting more agile

• Getting started
• Making the change sustainable

Requirements and Planning

• The product backlog. A list of prioritized requirements. 
• Ways of managing requirements. IEEE style, use cases, user stories. Advantages/disadvantages
• Estimating the requirements, story points vs ideals days
• prioritizing requirements to optimize customer satisfaction and ROI
• Release planning, meeting the "goal", status tracking, buffers etc
• Iteration planning, setting a goal, breaking down requirements and committing as a team
• Key to agility: Definition of Done
• Exercises: Writing user stories, Estimating as a team, Iteration planning

Running the iteration

• Daily Scrum. Synchronize team activities through a short daily standup meeting
• Project tracking. Showing progress visually with a task board and burndown charts
• Exercises: Daily Scrum (with hidden agendas... ), Ten second coach, Scrum simulation

Demonstration and reflection

• Sprint Demo. Showing progress and getting feedback from stakeholders
• Sprint Retrospective. Continuous improvements through reflection on what worked and not during the iteration

Agile above team level

• Organizations

• Outsourcing

Engineering Practices

• XP, the engineering practices that fits like a glove with the project management practices of Scrum
• Exercise:  Pairing

partners

• Contracts and cooperation
• Exercises: Pairing (without programming), Money for nothing, change for free