Skip to content

Breaking down an issue with a Similarity Principle

Remember your typical issues and try to identify the activities you usually engage in

Use my list only as an inspiration to start creating your own flow

The typical set of subtasks for a Software Development role includes:

  • [DEV] Review the Specifications for the feature
  • [DEV] Create an Arch design for the feature
  • [DEV] Choose Frameworks or Internal Solutions for the feature
  • [DEV] Create Data Models for the feature
  • [DEV] Divide your work into subtasks based on the program structure
  • [DEV] Prepare the Merge Request for the Code Review
  • [DEV] Implement Monitoring and proper Logging for the feature
  • [DEV] Create Unit Tests for the feature
  • [DEV] Fix bugs found after Testing
  • [DEV] Introduce Integration Tests for the feature
  • [DEV] Prepare a Deployment Instruction for the feature
  • [DEV] Support Deployment of the feature to the Production Env

Tasks commonly associated with a Software Testing role involve:

  • [QA] Identify the main risks for the feature
  • [QA] Review the specifications for the feature
  • [QA] Create User Acceptance Tests for the feature
  • [QA] Prepare a Test Environment
  • [QA] Automate selected test cases for the feature
  • [QA] Make an Exploratory Testing of the feature
  • [QA] Make the Whole System / Integration Testing with the feature
  • [QA] Test non-functional requirements for the feature
  • [QA] Make a Post-Deployment Verification of the feature
  • [QA] Test the feature in the Production environment
  • [QA] Create Test Strategies for the feature
  • [QA] Produce a checklist, test cases, or BDD tests
  • [QA] Break down work by a functionality domain
  • [QA] Prepare test Data for further Testing
  • [QA] Run Regression Tests with the new feature

An Analyst role typically entails a set of subtasks like:

  • [Analysis] Observe how users use related features
  • [Analysis] Analyze logs and monitoring data related to the feature
  • [Analysis] Suggest pros and cons of implementing the feature
  • [Analysis] Determine the business value you can get from implementing the feature
  • [Analysis] Collect the feedback and create specifications for the selected solution
  • [Analysis] Monitor the behavior and performance of the feature in Production
  • [Analysis] Collect feedback on how the feature satisfies the needs
  • [Analysis] Explore user Data to find some insights
  • [Analysis] Make a market research
  • [Analysis] Test Ideas and Models of a Potential Feature
  • [Analysis] Prototype Solution and get Internal Feedback