Blameless Post Mortem Meeting Template
Production incidents are the worst kind of lean IT waste. To prevent them, we use Blameless Post Mortems. These meetings dissect events, identify actionable steps, and ensure no blame is placed on individuals. The goal is to automate repetitive tasks and foster a culture of open communication to avoid future incidents. This approach stops the cycle of blame and ensures continuous improvement and learning.
def of_ready(*args, **kwargs)
The Definition of Ready (DoR) ensures agile stories meet criteria before entering the value stream. It helps prevent waste and inefficiencies, ensuring stories are valuable, testable, and understood by the team. DoR includes value, clear acceptance criteria, known dependencies, and consideration of testing and non-functional requirements. It streamlines processes and reduces bottlenecks.
We Call it ‘Saw Time’
"Saw Time" at Dev3loper.ai empowers professionals with dedicated learning hours during business days. Like initiatives at tech giants, it prioritizes individual growth over routine tasks. Backed by top-down support, it fosters a culture of continuous learning and craftsmanship. This approach enhances team agility and innovation, ensuring sustained product excellence and professional development.
A Cultural Target State: Netflix
I recommend the Netflix Culture Slides for insights into organizational culture. At OnShift, we value our engineering culture. Inspired by leaders like Spotify and Netflix, we aim to scale with good fundamentals and common sense. Key themes include values, high performance, freedom & responsibility, context over control, alignment, top market pay, and promotions.
Definition of Done
The Definition of Done (DoD) is a key Agile concept ensuring user stories meet specific criteria before being considered complete. It establishes clear, common terminology for all team members, eliminating ambiguity. Benefits include explicit accountability, clarity, preventing story thrashing, reducing misunderstandings, and guiding pre-implementation activities. A typical DoD checklist includes code updates, formatting, reviews, tests, documentation, and addressing performance, security, and metrics.
Defect Definition of Ready
Defining a "Defect Definition of Ready" ensures defects are thoroughly documented before team review, saving time and resources. A good bug report should include a clear title, summary, reproducible steps, expected vs. current behavior, priority, frequency, context, and any relevant screenshots. This approach reduces churn, enhances team accountability, and improves tester-developer relationships.
Definition of Ready
The Definition of Ready (DoR) is a checklist ensuring a product backlog item is prepared for a sprint. It prevents pulling in unready stories and releasing incomplete ones. DoR doesn't mean a story is 100% defined but must meet certain criteria. Benefits include avoiding time wastage, reducing scope creep, and keeping the team accountable. Key questions: Why, What, and How/Who. Regular backlog grooming and an example checklist ensure clarity and readiness.
Get In Touch
We'd love to hear from you! Whether you have a question about our services, need a consultation, or just want to connect, our team is here to help. Reach out to us through the form, or contact us directly via social media.