Develop Task Checklist

All work in the Scrum Backlog is represented with JIRA issues. The Develop Agile Board has four columns that we use to handle a JIRA Task or Story Issue (To Do, Code Review, User Testing, Success). Before pulling an issue to the next column, please review each essential checkpoint for the current column. 

 

Work Plan

StatusTO DO

Sprint

 

JIRA Issue

 

Developed By

 

Reviewed By

 

Tested By

 

Cartoon showing Dilbert running down his wearable checklist.

 

 

To Do Column

 TopicBefore moving an issue to In Progress ..(tick)

(minus)

(warning)

Remark
1Definition of SuccessDoes the Description includes a clear, testable Definition of Success and one or more user stories?
  •  
  •  
  •  
 
2Work Right to LeftHas any other issue on the board been assigned back to you? If so, do that one first.
  •  
  •  
  •  
 
3

Limit Work in Progress

Is any column overloaded? (a column turns red if it has too many issues).

  • If so, please try to move an issue in an overloaded column before starting another issue.

  •  
  •  
  •  
 
4Collective OwnershipAre you sure no columns are red, and you cannot work right to left first?
  •  
  •  
  •  
 

(tick) Yes - (minus) No - (warning) Not Applicable

 

In Progress Column

 TopicBefore moving an issue to Code Review ...(tick)

(minus)

(warning)

Remark
1Test ExecutionDo new test methods execute in five seconds or less?
  •  
  •  
  •  
 
2Code CoverageFor new Apex classes, do we have 90% test coverage?
  •  
  •  
  •  
 
3Global DiligenceDo any new Global classes include API docs (ApexDocs)?
  •  
  •  
  •  
 
4API Regression TestsIf new Globals are added, is there a followup task to update the regression test suite?
  •  
  •  
  •  
 
5Deploy to PackageAre all new components added to the package.xml?
  •  
  •  
  •  
 
6Mock CustomerIs any sample data specified by the story entered into the task branch?
  •  
  •  
  •  
 
7Mock DataIs the export/import script updated for any new data components?
  •  
  •  
  •  
 
8Help for this PageFor any new tab, is a Help for this Page stub in place?
  •  
  •  
  •  
 
9Static AnalysisHave you run the SonarQube Incremental Analysis report and addressed any coding issues?
  •  
  •  
  •  
 
10Task BranchesIs the code pushed to a task branch named for the JIRA issue and a Pull Request created?
  •  
  •  
  •  
 
11User Stories

Are the core user stories to verify noted?

Is there at least one user story indicated?

[As a {role}, you need {feature} for {benefit}.]

  •  
  •  
  •  
 
12Test Suite

Is a test suite setup with scripts for the main success scenario and extension conditions?

And linked from the Testing Scripts field?

Are any special prerequisites or environment setup needs indicated?

  •  
  •  
  •  
 
13Change LogIs a change log entry included in the JIRA issue, with a brief description of the change, engineer to engineer, and citing the affected repository and key components?
  •  
  •  
  •  
 
14BlockersIs this a blocker or other priority issue? If so, ask someone to review and test it right away.
  •  
  •  
  •  
 

(tick) Yes - (minus) No - (warning) Not Applicable

 

Code Review Column

 TopicBefore moving an issue to Peer Testing ...(tick)(minus)(warning)Remark
1Pull Requests

Does the pull request target develop? Is it set to delete on merge?

  •  
  •  
  •  
 
2Static AnalysisDid the coder run the SonarQube incremental static analysis report and resolve any issues?
  •  
  •  
  •  
 
3Elements of Style

Does the code -- including the test code -- Observe the Elements of DreamOps Style?

  •  
  •  
  •  
 
4Dangling TodosIf the code comments includes To Dos, does the comment reference an upcoming JIRA issue?
  •  
  •  
  •  
 
5Apex TestsDo the Apex Tests contain direct, sensible assertions that exercise the Apex class APIs and follow other testing best practices?
  •  
  •  
  •  
 
6Tests as DocumentationDo the Apex Tests help you better understand how the code works?
  •  
  •  
  •  
 
7Fit for PurposeIs the code fit for purpose and without obvious side effects or defects?
  •  
  •  
  •  
 
8Trust but VerifyDoes the Apex Test History show that the Apex tests were run and pass?
  •  
  •  
  •  
 
9Test Cases

Does the scope and range of the test cases seem sufficient? 

  •  
  •  
  •  
 

(tick) Yes - (minus) No - (warning) Not Applicable

 

User Testing Column

 TopicBefore moving an issue to Success ...(tick)(minus)(warning)Remark
1Apex Tests

Do the Apex automated tests in the Pull Request pass?

  • If so, note as much in the Test Suite column, with an inline comment for the developer. 
  • If not, re-assign to the coder and move back to the To Do column.
  •  
  •  
  •  
 
2Test Scope

Are the features you tested noted in the Test Suite for this issue?

  • Did everything pass?

    • If not, insert comments to the developer and reassign.

  • Have you considered alternative usages and workflows along with the main success scenario?

    • If not, flesh out the test cases, and work it; work it hard.

  • Are you sure we considered alternative usages and workflows along with the main success scenario?
  •  
  •  
  •  
 
3Test Coverage

For this issue, do you feel that we now have adequate test coverage (manual and automated) in the test suite?

Ping the initial developer if you need more input to exercise the code

  •  
  •  
  •  
 
4Test SuiteDid the work product pass the Test Suite?
  •  
  •  
  •  
 
5

Exploratory Testing

Did you use the feature as part of a larger workflow?

Did you test nearby features that could be affected by the change?

Did you "test like a customer" and try to break the features under test by doing things you know are wrong?

  •  
  •  
  •  
 
6Pull RequestsIn the pull request, did the developer reduce ("squash") the changes into a single commit?
  •  
  •  
  •  
 
7Work LogHas everyone working on the issued logged their time (including yourself)?
  •  
  •  
  •  
 
8ChecklistHave all the prior checklist items been observed?
  •  
  •  
  •  
 

(tick) Yes - (minus) No - (warning) Not Applicable

 

Cartoon showing how Dilbert's Wally tests technology.

 

Test Suite - Standard

Test Case / Business Rule StepsExpectations(tick)(minus)(warning)
Unit Tests Pass
  1. Log into the appropriate task org.
  2. Browse to the Apex Test execution page.
  3. Click "Select Tests".
  4. Select and run all unit tests.
All unit tests should pass.
  •  
  •  
  •  
New classes have 90% unit test coverage
  1. Log into the appropriate dev org.
  2. Browse to the Developers Console.
  3. In the "Tests" tab find the unit tests you ran in Test 1.
  4. Find any new classes added by this ticket.

All new classes should have at least 90% code coverage.

  •  
  •  
  •  
UI elements look right on all viewports

Resize your browser to an approximate mobile viewport size.

 The built in development tools in Chrome make this simple

All visual elements fit overall design guidelines of and make sense to someone who's never seen them before.
  •  
  •  
  •  
Peer Test Case

Add an alternate or regression scenario that wasn't identified by the developer or product owner.

The peer identified test case passes as expected.
  •  
  •  

 

 

Test Suite - Success

#Test Case / Business Rule StepsExpectations(tick)(minus)(star)
1
  •  
  •  
  •  

(tick) Pass - (minus) Fail - (star)Automation Candidate