agile development at sokrati
DESCRIPTION
TRANSCRIPT
Process that transformed time-to-
market
Kaushik Paranjape
Scrum As a Process
• Philosophy of continuous deliveries in shorter iterations
• Cross-functional teams
• Product Backlog > Release Backlog > Sprint
• Process Steps
– Sprint Planning
– Daily Scrums
– Sprint Review (The Demo)
– Sprint Retrospective
• Metrics & Measurements
– Productivity: Team Velocity
– Progress: Daily Burndown
– Task & Requirements Churn
Scrum @ Sokrati
StoryboardingResource Planning & Cool-off
Execution Sprints
StoryboardingResource planning & Cool – off
Execution Sprints
Scrum @ Sokrati
• 1 + 3 approach (1 month storyboarding/maintainence + 3 month dev)
• Back-to-back sprints – Cooloff during Maintenance month
• Ops transitions every release
• QA cycle every release
• Lead Plans Sprint 1 week before it starts
Roles
Role ResponsibilityLead (L) • Ensuring the team is fully aware of the responsibilities and
the vision.• Ensuring the commitments are adhered to. Once the
commitments are made the team• Ensuring that the team has no road-blocks and the business
is fully aware of the team's deliverables• Lead is also the scrum-master of the sprints.
Product Manager (PM)
• Ensuring that the team is fully aware of the road-map for the next 4 months.
• Is a channel of communication between the stakeholders (clients + business owners) and the engineering
• Ensures that the features listed down for the next four months are coherent and complete.
• Ensures that the features listed are do-able. i.e. Technical Feasibility, User Accepted.
Team (T) The team is the party responsible for delivering the commitments. They will work very closely with the lead and ensure that the product that is delivered is complete and fully tested
Roles
Role Responsibility
QA The team rotates QA whose sole responsibility is to break the feature that is developed in the sprint. They have ensured that the feature that is to be released is robust and fully tested.
OPS Operations Engineering is responsible for the maintenance and support of the product.
OPS Rotational (OPSR)
Are individuals who will help transfer knowledge of the feature to the operational team. He/she is usually the QA of the previous sprint who has signed off on the feature and its requirements.
Agilo
Monitoring & Tracking
• Metrics
– Velocity (Stories completed per sprint)
– Task Overrun (Pending tasks)
– Task/Requirement stability (Number of unplanned tasks)
– Delivered value (Business value delivered in a sprint)
• Automated with Agilo
Release strategy
• 2 week releases
• PM discretion to tag a release as Alpha
• Every 3 month a big impact release
• Conditional beta releases
QA & Ops strategy
• Dev member to act as QA for each sprint
• There will be a QA, Lead, Ops transfer sprint in the milestone release
• Ops to have a handover checkpoints before taking for support
