Atlassian Engineering Practices

Implement Atlassian engineering practices for agile workflows and incident response.

Updated Jun 7, 2024
One-click install
npx skills add https://github.com/ashishgurprit/ANLP_A3 --skill atlassian-engineering-practices
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Atlassian Engineering Practices
Source: https://github.com/ashishgurprit/ANLP_A3/tree/main/.claude.backup/skills/atlassian-practices
Command: npx skills add https://github.com/ashishgurprit/ANLP_A3 --skill atlassian-engineering-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to implementing Atlassian's proven engineering best practices, helping teams improve their development processes, decision-making, and overall quality.

Core Features & Use Cases

  • Definition of Done (DoD): Ensures features are truly complete by providing a detailed checklist.
  • Agile Ceremonies: Outlines effective structures for Sprint Planning, Daily Standups, and Retrospectives.
  • DACI Framework: Facilitates clear decision-making by defining roles for important choices.
  • Health Monitors: Offers a framework for regular team self-assessment.
  • Incident Management: Defines severity levels and a structured response process for incidents.
  • Quality Assistance: Promotes a "shift-left" approach to quality, making it a team responsibility.
  • Code Review Guidelines: Establishes best practices for both authors and reviewers.
  • Playbook Plays: Includes techniques like Pre-mortems and 5 Whys for risk assessment and root cause analysis.

Quick Start

Explain the Atlassian Definition of Done checklist.

Frequently Asked Questions about Atlassian Engineering Practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the Atlassian Definition of Done checklist for agile teams?

The Atlassian Definition of Done checklist ensures features are truly complete by verifying code quality, testing, and documentation before sprint closure. It provides a structured framework to align agile team expectations and enhance project predictability.

How do I use the DACI framework for agile decision-making?

The DACI framework facilitates clear agile decision-making by assigning specific roles to team members for important choices. It defines who is the Driver, Approver, Contributor, and Informed to streamline project decisions.

What are the best practices for code review in software engineering?

Code review best practices establish clear guidelines for both authors and reviewers to improve software quality. They define structured feedback processes that enhance team collaboration and maintain high code standards.

How does incident management define severity levels and response processes?

Incident management defines specific severity levels and a structured response process to handle software failures efficiently. It integrates blameless postmortems to promote continuous improvement and resolve system incidents effectively.

Can I use quality assistance to shift-left testing responsibilities in my development team?

Yes, quality assistance promotes a shift-left approach that makes quality assurance a shared team responsibility. It integrates testing early into the software development lifecycle to boost overall code quality and productivity.

What agile playbook techniques help with root cause analysis and risk assessment?

Agile playbook techniques like Pre-mortems and 5 Whys help teams conduct root cause analysis and risk assessment. They provide structured methodologies to identify potential project failures and resolve underlying engineering issues.