Swarmia Boot Camp
Unlock your organizations potential and remove blockers with this Swarmia Boot Camp
Keeping track of your product’s engineering backlog has many benefits for the entire team. It ensures that every feature or bug fix is visible to everyone and reduces the risk of duplicated work.
Every engineer knows how challenging it is to manage tasks in a complex environment with multiple stakeholders, each with their own objectives and priorities. Keeping track of your engineering work can be a daunting task—even more so when you're working on multiple projects at once.
To help your team manage their work, you need to create a common vocabulary that they can use to describe their tasks. Team members might do this by writing down their individual objectives and priorities, followed by the product backlog.
Before starting your team's first project, decide who will be involved in the project and what will be required of them. If a single person is chosen, they should be charged with the entire project from start to finish. The team should then move on to another person assigned primarily to that particular task. It's handy for everyone to have a common objective and goal for the project at hand—even if it only involves a single engineering manager or two engineers from your new organization.
In addition to having an objective set, design documents also play an important role in managing work in your organization: identify which components of the technical infrastructure are most affected by work hours, identify dependencies between components, determine when there's an opportunity for cross-project collaboration, and so on. Design documents are good visibility tools because they help keep track of one's responsibilities cleanly when there's a single point of contact between all stakeholders in board meetings. They also focus on some key decisions that might arise during time management discussions—such as prioritizing tasks facing professional development groups or educating leaders about new software features or security breaches during an emergency response effort. In addition, design documents provide more human-readable content.
However, there's no need to worry. Even though the road ahead may seem challenging, there are plenty of ways you can bring order into your world of chaos and establish a reliable system that supports everything you need as an engineer. In this course, we'll explore how integrating Swarmia can help you manage your engineering backlog with ease and enhance your engineering process.
Duration2 days/16 hours of instruction
Public Classroom Pricing
GSA Price: $1185
Group Rate: $1195
Private Group Pricing
Have a group of 5 or more students? Request special pricing for private group training today.
Part 1: Introduction
- What Are Engineering Backlogs?
- Creating Your Engineering Backlog
- How to Find an Engineering Backlog in an Existing Project
Part 2: A General Overview of Scrum
- Sprint Planning
- Who is involved in the sprint planning process?
- What is a sprint?
- What is the purpose of a scrum sprint?
- Benefits of a scrum sprint
- Scheduled feedback loops
- Exercise: Create assignments in scrum.
- Exercise: Create documentation in scrum.
- Exercise: Identify, prioritize, and resolve blockers.
- Exercise: Commit updates and changes.
- Sprint Reviews
- What is a sprint review?
- What does it look like?
- Expectations from your team before the review
- Review process
- Exercise: Prepare for a scrum sprint review.
- Agile Methodology
- What is the agile method?
- Why build with agile processes?
- Continuous improvement
- Stakeholder involvement
- Collaboration everywhere
- Theories and concepts for managing projects in agile development
- Planning phase: define your work structure, define your milestones, and set deadlines
- Execution phase: get to know your team, ensure quality, track results, and take feedback
- Backlog Management
- Why backlog management is important in scrum
- When to manage backlogs in scrum
- Exercise: Create team and roles for backlog management.
- Exercise: Set up your team workspace.
- Best practices for backlog management
Part 3: Engineering Backlog
- Improving an Engineering Backlog
- Establish a workable process and a growth mindset
- Keep a project updated and organized
- Avoid vague engineering requirements
- Ensure an engineering backlog is consistent across teams
- Importance of Managing Your Engineering Backlog
- Exercise: Track team velocity using Swarmia Insights.
- Exercise: How to ensure consistency in project prioritization.
- Improving product roadmap
- Exercise: Drive product strategy by designing a software roadmap.
- Knowing when to sunset projects
- Managing time efficiently
- How Integrating Your Engineering Backlog Benefits Your Team
- Exercise: Log features for managing backlog.
- Exercise: Manage projects through backlog engineering.
- Exercise: Remove information silos.
- Tools for Managing Your Team's Engineering Backlog
- Exercise: Use GitHub Projects to manage your engineering backlog.
- Exercise: Use Jira to manage your engineering backlog.
- Exercise: Use ClickUp to manage your engineering backlog.
- Exercise: Use Swarmia to manage your engineering backlog.
Part 4: Getting Started With Swarmia
- What Is Swarmia?
- Overview of the Swarmia platform
- Swarmia and its management
- How does it work?
- How to set up a Swarmia environment
- Integrating Swarmia With Your Engineering Backlog
- Why Use Swarmia to Manage and Maintain Your Backlog?
- Using Swarmia for Backlog Management
Part 5: Swarmia Integrations
- Why Integrate Swarmia With Other Tools?
- Swarmia Integrations
- Exercise: Integrate Swarmia with Jira.
- Exercise: Integrate Swarmia with GitHub.
- Exercise: Integrate Swarmia with Slack.
Part 6: Backlog Tracking in Swarmia
- Tracking Tasks and Issues
- Exercise: Import tasks and issues.
- Exercise: Add issues to your engineering backlog.
- Exercise: Export all data to Excel—your backlog and issues only.
- Tracking Product Roadmaps and User Stories
- Shortcut to your sprint backlog and burndown charts
- Exercise: Track defects on a product roadmap.
- Exercise: Allocate tasks to user stories and epics.
- Tracking User Research and Requests
- Why is tracking user research important?
- Exercise: Track user research and requests in Swarmia.
- Exercise: Create artifacts for user requests tracking in Swarmia.
- Tracking Development Workflow Automation Tasks
- What are development workflow automation tasks?
- Why are they important?
- Exercise: Track development workflow automation tasks in Swarmia.
- Exercise: Assign development workflow automation tasks in the backlog?
- Exercise: Track product roadmap and user stories in Swarmia.
Professionals who would benefit from this training include:
· Software Developers
· Quality Assurance
· Product Owners
· Development Team
- Define the core concepts of Agile Engineering Backlogs
- Participate in Sprint Planning & Execution
- How to improve engineering backlogs
- Understand how to get started with Swarmia
- Use Swarmia for backlog tracking