You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Please review Custom Development Request to understand the overall custom development process. 

This guide will cover the Functional Specification and Build process.

Similar to the request process, the same Jira project will be used to manage build. Following are the links to the Build boards.

Release 2 Build Board

Release 4 Build Board

Functional Specifications (FS)

Creating Functional Specification

Before drafting function specifications, user must create a "Development" card in Jira for each FS as mentioned below. 

  1. Create a Development card in the corresponding Jira Build board.
  2. Please take note of the Jira key. It will be used as a pre-fix for the FS title.
  3. Update the details under Overview tab. Leave the assigned developer or tech reviewer field empty and the development team will update it. 
  4. Dependent Builds (i.e., FS from the same request card) will be lined using linked work item methods.
    • Click on "+ Add" and selecting "Linked work item".
    • Choose "is related to" relationship and linked to the request and related development card. All development card are expected to be linked to its request card. 
      Please note that the linked work item are not transitive. Meaning if A & B are linked and B & C are linked, A & C are not automatically linked and users will need to create the link between A & C. 
       
  5. .Related Builds (i.e., different request card) should be group together using the "Custom Development Grouping".

Note

It it the functional consultants responsibility to link and group dependent and related builds so that the development team can plan the build accordingly. 

After creating the development card, it will be in "FS in Progress" status and user can start drafting their FS in Confluence. Please refer to Creating Functional Specifications using Scaffolding Templates.

Functional Specification Review and Approval Process

The following diagram describes the FS review and approval process and the corresponding statuses are highlighted in blue.

Build Process

The following stages will be managed in Jira. 

Jira StatusActivityPIC*

FS in Progress

  • Use Jira key from the corresponding Development work item as the prefix for the FS title and draft FS in Confluence
  • Follow the document workflow in Confluence until FS is signed off

Functional Consultant

FS Approved

  • FS Signed-off
  • In queue for development
Functional Consultant

Build in Progress

  • Build custom object
Assigned Developer

Unit Test in Progress

  • Perform unit test
Assigned Developer

Build Ready for Tech Review

  • Perform code and build review
Tech Reviewer

Build Ready for FAT

  • Perform function acceptance test (FAT)
Functional Consultant

Issue Resolution

  • Fix issues reported by functional consultant
Developer

Completed

  • Sign-off on build
Functional Consultant

* PIC - Person who will perform the activity and move the Jira card to the next stage.

During the build process, tech reviewers have the permission to move the cards to the following statuses and reinstantiate.

  • On-Hold - If build is to be paused.
  • Descope - If build is not required. 






  • No labels