Project Setup
The initial project setup for a Scrum Lite implementation is the very similar to a traditional Scrum project.
Scrum Lite simplifies several pieces. See call-outs below for details.
1. Form the Core Team
- Appoint a Product Person who will be responsible for maximizing product value and managing the product backlog.
- Designate a Project Manager to facilitate the process, remove impediments, and ensure development practices are followed.
- Assemble the Development Team (typically 3-7 members) with cross-functional skills needed to deliver the product, at minimum:
- Full-stack software engineer
- DevOps engineer
- UX designer
Maximum of 7 on a Development Team: 3 Developers, 2 DevOps, 2 UX.
2. Create the Product Vision
- Conduct a vision workshop with stakeholders.
- Define the product's purpose, target users, and key benefits.
- Document high-level goals and success criteria.
- Establish alignment with organizational objectives.
3. Develop the Initial Product Backlog
- Work with stakeholders to gather requirements.
- Create user stories that capture customer needs.
- Prioritize items based on business value.
- Break down large items into smaller, manageable pieces.
- Add initial estimates to help with planning.
4. Plan the Release
- Define the release schedule and milestones.
- Determine sprint length (typically 2-4 weeks).
- Set initial velocity assumptions.
- Create a high-level release roadmap.
- Identify dependencies and risks.
5. Set Up the Environment
- Establish the physical and/or virtual team workspace.
- Select and configure necessary tools:
- Project management software
- Version control system
- Continuous integration/deployment (CI/CD) pipeline
- Communication platforms, including:
- audio, visual, text
- charts, graphs, etc.
Communications platform requirements should be discussed with the stakeholders. Some available tools have robust sets of charts and graphs; however, what ultimately needs to be communicated is what the stakeholder needs.
6. Define Working Agreements
- Establish Definition of Done (DoD).
- Create team working hours and availability expectations.
- Set communication protocols/expectations.
- Define quality standards and coding guidelines.
- Agree on testing and documentation requirements.
7. Plan the First Sprint
- Conduct the initial Sprint Planning meeting.
- Select items from the Product Backlog.
- Break down items into tasks.
- Create the Sprint Backlog.
- Set the Sprint Goal.
8. Establish Good Communication Habits
Good communications supersede ceremonies.
- Development Team communications
- Project Management communications
- Sprint Planning (1-2 hours)
- Sprint Review with Stakeholders (1 hour)
- Set up backlog refinement sessions as necessary.
- Every meeting should have a published agenda.
With good communication habits, when meetings must occur they can be shorter, more focused, and, in some cases, avoided entirely.
9. Launch and Monitor
- Begin the first sprint.
- Track progress daily.
- Collect metrics and feedback.
- Adjust processes based on team needs.
- Document lessons learned.
10. Continuous Improvement
- Regular process evaluation.
- Team feedback incorporation.
- Adjustment of practices as needed.
- Ongoing training and skill development.
- Regular stakeholder engagement.
Remember: Agile is about being adaptive, adjust these steps based on your team's needs and organizational context.