Skip to content

Instantly share code, notes, and snippets.

@swapnilshrikhande

swapnilshrikhande/README.md

Last active May 19, 2022 04:29
Show Gist options
  • Save swapnilshrikhande/834ebaad2e1a31bd700ec7621ffcee9e to your computer and use it in GitHub Desktop.
Save swapnilshrikhande/834ebaad2e1a31bd700ec7621ffcee9e to your computer and use it in GitHub Desktop.
Download ZIP
System Development Analysis Checklist
Raw
README.md

Per Requirement Analysis Checklist

  1. Possible way to approach the requirements to frame right set of questions ? - [ ] Which is the core domain problem system will be resolving or we will be automating ?
    • Business Domain - Eg. Automating Sales Process
    • Technical Domain - Eg. CTI Integration, Salesforce Sales Cloud Implementation
    • What is the need of the system ?
    • Who are the end users of the system ?
    • Who are the super/admin users of the system ?
    • Are any existing business processes directly affected in any way ? i.e.
    • Will users need to alter the way they work today after this requirement is implemented, is that change acceptable to all stake holders.
    • Requirement Input Definition
    • Final output of the requirement
    • Which are other systems involved ?
    • How the Data is expected to flow within the system ?
    • What the system should not do ?
    • Which business process will generate the data?
    • Which business process will consume the information?
    • Transactions and individual transaction timelines ?
    • Is this module part of the core business flow ?
    • Client competencies to understand the requirements / use the platform and the business requirements
  • Frame questions based on above requirement analysis
  • Based on answers received for the above step, divide the requirement into Modules - Stories - Tasks - SubTasks
  • Point the Stories
  • Estimate the Tasks - Use PERT

Per Story Development Checklist

  • Requirement Live Document : Descriptive : Attach to Use Case Feature
  • Requirement Document : Use Cases (G-W-T) : Salesforce
  • Implementation : Design Solution Approach Document & Diagrams - Create and attach to Smartsheet task
  • Tasks - Review Estimates Kanboard Task / Subtask
  • Acceptance Unit Test Method mapping to use cases
  • Log time Kanboard Task / Subtask
  • Update Status : Kanboard & Smartsheet
  • Peer QA - Fixes
  • Ongoing Change Set / Deployment / Release - Plan attached to the release ticket.
  • Relevant comments on business : use cases and technical : smartsheet , internal : kanboard / update mminutes doc
  • Code commit and add commit link to the task ticket and create a pull request for code review
  • Code Review Comments : Kanboard
  • Update User Manual
  • Update Admin Manual
  • Update Developer Manual
  • Update Release Plan

Pre Deployment Checklist

  • Pull and commit dev code in dev-backup branch
  • Run all test methods in developer
  • Pull and commit staging code in staging-backup branch
  • Run all test methods in staging
  • Pull and commit prod code in prod-backup branch
  • Run all test methods in production

Note : Proceed with deployment only if all the functional test classes are passing.

Post Deployment Checklist

  • Run existing test classes
  • Custom setting configuration
  • Custom label configuration
  • Enable any required custom components : Workflows / Process / Approvals / Flows
  • Profile / Permission Set Permissions
  • Page Layout / Lightning pages configuration
  • External system configurations : External CTI / Website / Integrated system
  • Use Case QA Checklist & Fix any issues found or find a workaround
  • Delete Test Data
  • Handover system to client for QA with issues found and workaround document
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment