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 on : how to raise and approve endorse custom development requests for Release 2 and 4. The custom development process will be categorized into 2 phases: Request and Build. process for Functional Specification and Development will be updated later.

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 for SyWay. 

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.
   2. See 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 will initiate the review. As update "Tech Review" tab. As part of the review, the tech review will assess reviewer will perform the following
   1. Review the request and ensure clean core principles are adhered. 
   2. Assess the Tier, Count and
   Effort
   1. build effort. For more details on the Tier and Count, please refer
   to 
   1. to Development Id Definition and Counting Rules.
   2. 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 based on the custom development tier. 
6. Tier 3 needs to be justified in detail before DA approval and is only allowed by exception. It is legacy and considered deprecated. In certain circumstances classic ABAP development must be used due to lack of clean core replacements. These special cases are considered Tier 2.
7. Tier 2 needs to be justified in detail before DA approval. SAP is still adding clean core compliant APIs and enhancements each release and using tier 2 offers the needed flexibility to achieve the successful implementation of a business requirement.
Tier 1 is clean core compliant and upgrade stable. No detailed justification is needed from a tool or technology point of view before DA approval

*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

Creating Request

...

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. 

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.

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

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 Modified 

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

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.

Contact

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

...