Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The custom development process will be categorized into 3 phases: Request, Functional Specification and Development. 

The purpose of this guide is to outline the Request process: how to raise and endorse custom development requests. The process for Release 2 and 4.

Overview

Custom development process will be categorized into 2 phases: Request and Build and Jira will be used to manage the request and build processFunctional Specification and Development will be updated later.

draw.io Diagram
bordertrue
diagramName
Dev Process
Untitled Diagram-1749132798793
simpleViewerfalse
width
1000
1200
linksauto
tbstyletop
diagramDisplayName
lboxtrue
diagramWidth
1295
1879
height
310
476
revision3


Jira will be used to manage the request and build process. See Introduction to Jira for a quick overview on how we will use Jira. 

Info

Custom Development Request Process

  1. Raise request using Jira and move request to "Ready for Tech Review".
    1. See Creating Request for details on how to use Jira
    . See Raising Custom Development Request for details
    1. .
    2. Fill up all the details under "Overview" and "Supporting Information" tabs. See Request Instructions on how to complete the form. 
  2. Technology team will monitor the request under "Ready for Tech Review" and update "Tech Review" tab. As part of the review, the reviewer will perform the following
    1. Review the request and ensure clean core principles are adhered. 
    2. Assess the Tier, Count and build effort. For more details on the Tier and Count, please refer to Development Id Definition and Counting Rules.
    3. Identify Functional Specs to be created and the corresponding build object. 
  3. Once Tech review is completed, the tech review will move the card to "Ready for DA Review"
  4. On a weekly basis PMO will consolidate the requests and add them to the Design Authority (DA) agenda.
  5. The Design Authority will review and endorse requests.

*After DA endorsement, if a new Tier 3 custom object is required or the development tier increases to 3, DA endorsement is required again. Please contact MUTHUSAMY-ext, Kunalan or any DA members to move the original Jira Request to the initial stage and update the the request with the new details before following the request process.

Anchor
Req
Req

...

Raise request using form

Creating Request

  1. Login to Jira and go to the SyWay project
  2. From here you can create a request by clicking the "Create" blue button.
    draw.io Diagram
    bordertrue
    diagramNameS1
    simpleViewerfalse
    width600
    linksauto
    tbstyletop
    lboxtrue
    diagramWidth985
    height319
    revision3


  3. This will launch the following form. Please take note of the following:
    1. Under work type select "Request" to raise a request (do not use Epic).
    2. Please remember to choose the release or you will not be able to see your request on the board. 
    3. If you do not see the correct fields as shown below. Click on the 3 dots → "Configure fields" → Choose all fields.
    4. Fill up all the fields under "Overview" and "Supporting Information" tab.
    5. If you do not have all the information, you can still click create. The request will be added to the draft column and you can update it later
    Login and fill up the form. Please make sure you fill up the "SyWay Release" else your request will not be displayed on the board.
    After submitting the form, login to Jira. The link should take you to SyWay project (highlighted in red). If you are not in SyWay project, go to "Project" → "View all projects" and search for SyWay project
    1. .
      draw.io Diagram
      bordertrue
      diagramName
    S1
    1. s5
      simpleViewerfalse
      width
    600
    1. 400
      linksauto
      tbstyletop
      lboxtrue
      diagramWidth
    985
    1. 635
      height
    317
    1. 1204
      revision
    2
    1. 1
  4. After drafting the request, click create and the request will be under "Draft" column. Once all the details are provided, move the request  Search for your request under draft column and move it to "Ready for Tech Review" column.

Raising request from Kanban board

...

  1. Please note, as a requestor you only have permission to move the request to "Ready for Tech Review" and "Draft". subsequent status update will be managed by technology team and DA.

Alternatively, you can also click on the "+ create" under the draft column. This will create a card, choose "Request" work type, enter the title and hit enter. This will launch the request. As mentioned above, fill up all the fields under "Overview", "Supporting Information" tab and "SyWay Release" on the right side

...

.

draw.io Diagram
bordertrue
diagramName

...

s3
simpleViewerfalse
width600
linksauto
tbstyletop
lboxtrue
diagramWidth

...

1095
height

...

186
revision2

...

Anchor
form
form
Request Instructions 

Fill up all the details under "Overview" and "Supporting Information" tabs

For instructions on how to populate each field, place your cursor over the tooltip. 

Image Added

Important notes:

  • Custom Development Grouping - To group related custom object requests. Please ensure the exact same text (including case and spaces) are entered into the different request, else Jira will not be able to group them.
  • Type of development - Refer to Development Id Definition and Counting Rules.
  • Justification - Explain why standard SAP does not meet requirements and custom development is required. This field will be reviewed by DA before endorsing. 
  • Project Plan Details - State the project plan tasks name that corresponds to the request. If there is no task, please state as N/A.
  • Tech Review Comments - Tech reviewer to list down Functional Specs to be drafted.

Anchor
intro
intro
Introduction to Jira

Jira Kanban boards will be used to manage development.

The Jira work type "Request" has been customized for SyWay. Please do not create any other types of work type.

Separate boards are created for Releases 1, 2 & 4. Click on the dropdown to access the respective boards.

draw.io Diagram
bordertrue
diagramName

...

Intro 1
simpleViewerfalse
width600
linksauto
tbstyletop
lboxtrue
diagramWidth

...

1165
height

...

316
revision1

...



After a request has been created, Jira will assign a key labeled "ERP-##" and we will use this key to reference requests.

draw.io Diagram
bordertrue
diagramName

...

intro3
simpleViewerfalse

...

linksauto
tbstyletop
lboxtrue
diagramWidth

...

386
height

...

191
revision1

...

 

5 columns have been configured to manage the status of custom development requests. Cards are moved between statuses through a basic workflow:

  • Requestors have access to move a request between "Draft" and "Ready for Tech Review".
  • Technology reviewer has access to move request to "Ready for DA review"
  • The Design Authority has access to move requests to "DA endorsed", "Reject/Withdrawn" or back to "Draft

Image Added 

Use the search or quick filter to view requests created by you or in your work stream.

draw.io Diagram
bordertrue
diagramNameintro4
simpleViewerfalse
width600
linksauto
tbstyletop
lboxtrue
diagramWidth876
height614
revision1


The boards filter request based on the "SyWay Release" field. If your request cannot be found on both board, most likely the release is not set. Go to "List" and search for your request

...

.

draw.io Diagram
bordertrue
diagramName

...

Intro2
simpleViewerfalse
width

...

600
linksauto
tbstyletop

...

lboxtrue
diagramWidth

...

2162
height

...

550
revision1

Contact

If further clarification or assistance is required, please contact the following members from technology team.