Agile methodologies have become a mainstream component in the world of software development. Not surprising, Agile methods can be applied to many other types of business work. In our Agile Boot Camp for Non-Software Work, we apply agile techniques to addressing business processes, infrastructure, operations, and other types of work.
While not a silver bullet, Agile Methodologies have become the most practical way to create outstanding results. We will look at leading Agile methodologies for both discovery and operational work. You will learn the basic concepts behind Agility and how Agile can help you in your daily efforts.
In this course, you will:
- Gain knowledge of Agile principles, concepts, and mindset and understand why they are so important for each team
- Apply these concepts to work other than software development
- Follow the team approach; start as a team, finish as a team â€” and focus on delivering value to the organization
- Understand the power of the teams and typical agile team roles
- Learn Agile approaches for sustainability, infrastructure, operations, and non-IT work
- Understand when to use methods like Scrum or Kanban
- Learn methods that support incremental and emergent projects but also continuous flow work
- Embrace Agile planning techniques and recognize the value of continuous planning
- Map and visualize workflow to eliminate bottlenecks and streamline capacity
- Achieving a continuous improvement culture and Practice and maintain a regular cadence for delivering work
Course Outline1. Why Agile? The Case for ChangeBusinesses have historically been plagued by many problems, including inadequate requirements, which lead to products that customers aren't happy with and sometimes can't use.Â We start the class by making the case for a shift to an Agile approach to solve the problems and to gain an overall understanding of the basic principles, and benefits of Agile approaches.
Team Exercise: As a class we will discuss the various problems that the class has experienced in their own projects so that we can then understand how Agile will help them address these problems.Â The class will understand from this exercise that they are not alone with a set of problems that others also experience.
2. Becoming AgileWe will understand the Agile Manifesto and Principles. We first visit Lean which is foundational and influences all other Agile methodologies.Â Then we will have an overview of Scrum.Â Scrum is the most popular Agile methodology and is great for projects.Â Scrum or Scrum variants are being used by about 75% of those using Agile, but Scrum is not the only Agile approach.Â We'll then see how Kanban might be a better answer for other types work (e.g. operations and sustainment).
Review Agile methodologies practiced in organizations today (e.g. Scrum, Kanban).
- Agile Mental Models
- Agile Manifesto
- Agile Principles
- Agile Practices
Team Exercise: Teams will engage in a fun exercise that will reinforce the importance of, and power behind, self-organizing teams. As with sports teams, individual roles are important, but even more important is the need to work toward a common goal together. At times that means blurring the lines of traditional roles. Great teams will not define themselves by their individual roles.
3. Building an Agile TeamAgile focuses on creating a team that can deliver results over and over.Â In this section we will discuss what makes a high-performing team and how to build that team.Â The section will also cover the team roles associated with an Agile approach.
Team Exercise: We will discuss as a class what makes a great team based on teams we've participated on that were great.
4. Delivery with ScrumIn this section we will review the Scrum framework and the various Scrum techniques. Scrum provides a great framework for building new products, especially when all the requirements are not known. Scrum techniques can also be used with other Agile methods like Kanban.
Agile Project Planning
- User Roles and Personas
Team Exercise: Teams will practice turning User Roles into full fleshed personas.
5. Backlog Planning
- Writing User Stories
Team Exercise: Each team will conduct a brainstorming session for creating a product backlog in the form of user stories. Each team will present some of their user stories and the instructor will lead discussion about where teams hit the mark and areas for improvement (Instructor will not have all of the ideas, this is a great opportunity for team dynamic).
6. Iteration Execution
- Â The Daily Scrum
- Â Story Review
- Â Visual Management
- Â Agile Metrics
7. Inspect and AdaptThe power of Agile comes from the fact that continuous improvement is built into the Agile system.Â In this section we will review how People, Product and Process improve themselves through a frequent inspect and adapt process.Â We will discuss the main Agile ceremonies that help us accomplish this: Iteration Review/Demo and the Retrospective.
- The Iteration Review
- The Demo
- The Retrospective
Team Exercise: Teams will discuss what things they can do the day after class ends to take what they've learned and implement it immediately so that they don't lose what they've learned.
8. Kanban Overview and ConceptsNot all work fits well into a Scrum framework. Kanban is an Agile method that helps us to improve a delivery process with a focus on continuous improvement. We will cover the foundation of Kanban concepts, properties, and terminology. We will also understand the philosophy behind the Kanban framework and how it originated.
- Kanban's 5 Core Properties
- Kanban Emergent Behaviors
- Kanban concepts, principles, and terminology
9. Implementing KanbanThe best way to understand Kanban is to go through the process of implementing it. This section goes through the various techniques and ceremonies associated with Kanban.
- Visualization of Work
- Work Item Types, Card Walls
- Workflow, Queues and Buffers
- Cadences, Work-in-Progress
- Bottlenecks, Issues and Blocked Items
Team Exercise: Kanban boards are an invaluable communication tool. Each team is tasked with coming up with their board that clearly communicates their commitments and progress against those commitments.
10. Kanban Metrics and ReportingKanban uses metrics a little differently than other Agile methods. In this section we will understand how metrics and reporting are leveraged with Kanban.
- Tracking Work-in-Process, Cumulative Flow Diagrams
- Lead Time, Trends, Throughput
11. Scaling KanbanApplying Kanban techniques to other types of efforts. How to track requirements, decouple work, and leverage the Minimal Marketable Release.
- Scaling Kanban for different size efforts
- Minimal Marketable Release
- Two-Tiered Card Walls
Â 12. Kanban ImprovementsLearn how to recognize opportunities for improvement in your Kanban system and what to do about them.
- Three types of Improvement Opportunities
- Estimations, Class of Service
- Service Level Agreements, Policies
Team Exercise: Teams will build a cadence calendar to use with their teams to organize work, share learnings, and build a focus on continuous improvement.
13. Agile AdoptionAgile Adoption can be accomplished with different approaches and at different speeds.Â In this section we will review the best practices of Organizational Change Management as it applies to an Agile adoption and consider the primary reasons for adoption failure.Â
- Kaizen Culture and Mindset
- Agile Leadership
- Kotter's Model
- Continuous improvement culture
Team Exercise: We will wrap the course up and end with a discussion on â€œWhere do you go from here?â€.
Who should attend
This course is designed for anyone who wants to apply agile techniques to their own work, even if it's not software related.
Because this is an immersion course and the intent is to engage in the practices every Agile team will employ, this course is recommended for all team members.
That includes, but is not limited to:
- Anyone wanting to apply Agile to their work, even if not software related
- Business people wanting to apply Agile to their business projects and processes
- Infrastructure, Operations, Sustainability, Support Services staff
- Teams and individuals doing non-IT work, projects or continuous flow work
- Teams and individuals who support or work with other Agile teams
- Specialty Teams, Transactional Teams
- Even software developers will benefit!Â
If a change needs to be made to your public course registration (cancel, transfer, or substitution) ASPE must receive written notice via email at email@example.com or fax at 919-816-1710. If a cancel or transfer request is made less than 15 business days prior to the class start date, payment will still be due, no refunds will be issued and you will be charged a $200 change fee. Your paid tuition will be available for one year to be used as a credit towards another course of equal value; only one reenrollment opportunity is allowed. Failure to attend the course without written notification will result in forfeiture of the full course price. Student substitutions may be made at any time prior to the start of class free of charge. If ASPE is forced to cancel a course for any reason, liability is limited to the registration fee only.
Your City, Your Province