Appearance
🔹 Working Model
For the upcoming period, we will not work in Sprint-based delivery.
The team will shift to a Feature-based approach ( Kanban Workflow )
🔹 Roles & Responsibilities
Testers will be responsible for:
Handling and clarifying business-related questions
Attend the grooming session and ensure that acceptance criteria are clear, complete, and ready for the development team.
Prepare detailed test cases for each user story.
Prepare and maintain the Postman collection for related APIs.
Explain the prepared test cases to the team during the planning meeting.
Scrum Master will be responsible for:
Follow up on feature progress and ensure smooth delivery.
Identify and remove blockers.
Ensure all tasks are created, assigned, and tracked on the board.
Protect Work in Progress limits to ensure smooth flow and avoid overloading the team.
Continuously improve the process by identifying gaps, facilitating improvements, and following up on action items.
Tech Leads will be responsible for:
Technical guidance and technical decisions
Supporting the team from a technical perspective
Create API Contract
Senior Developers will be responsible for:
Technical guidance
Supporting the team from a technical perspective
Create API Contract
🔹 Meetings & Cadence
A weekly Grooming Session and Planning Meeting will be held with fixed schedules.
Grooming Session attendees:
Tech Leads
Senior Developers
Testers
Business Team
Scrum Master
🔹 Pre-Planning Activities
After the Business Team presents the user stories during the grooming session, the following activities must be completed before planning meeting:
Technical Design (API Contract)
Testers: Prepare test cases
Business Team: Review and validate test cases
Testers: Prepare Postman collection
Tech Leads: Assign developers to each feature
🔹During Planning Meeting, the User Stories will be explained from both business and technical perspectives.
Developers assigned to features will add estimated times for each task on the board.
🔹 Board & Task Management
All tasks must be:
Added to the board also including API Contract and Postman collection tasks
Assigned to an owner
Have a clear due date, original time time spent
Have a clear time spent after finishing the task
Important Note: To respect Work in progress limit, each team member should work on one active task only.
A new task can be pulled only after finishing the current task.
🔹 Readiness Criteria
For a user story to be ready for development, it must have:
Clear and agreed Acceptance Criteria
UX design, if required
Clear Test Case