SAP Hybris-SAP Commerce Cloud Development Process Guide Lines Should Be Followed

 

• A Developer has to follow the below process in his/her development for better tracking of tickets.

• Developers has to cross-check below items before picking a ticket:

  1. Fix Version - should be the current sprint

  2. Sprint - should be the current sprint

  3. Product Owner

  4. Work Stream - SAP Commerce or AEM

  5. Priority - ticket has to be prioritized by BA or Scrum Master

• Once we have all of these for ticket. Developer has to do below tasks:

1. Analysis, Technical Feasibility - Developer will analyze ticket and come up with any doubts or if something is technically not possible or any other better solution

2. Tech Design Preparation and Approval Process - Based on the complexity of the stories, technical design might be needed. Below criteria can be used to determine the need of tech designs. Once the tech design is completed, assign to the architects for review and approval. Create a subtask for the tech approval task and keep Story as Tech Approval status. Subtask should be In Review when assigning for review with proper comments.. Once review is completed and approves, status should be Closed with proper comment.

   • New EPIC

   • Performance Improvement changes as it is altering the existing design

   • Any change affecting both Hybris and AEM and/or SAP.

   • Any major technical introduction like Active Directory Enhancement.

   • Any implementation with the introduction of new libraries.

3. Update Estimates - Developer has to come up with estimate on number of hours required to complete given ticket along with Sprint points (if this ticket is a story)

4. Update Labels (If applicable like Hybris_BE, Hybris_FE)

5. Create any sub tasks (if required, have them added to sprint by Scrum Master)

• After this, Developer will change ticket status to In Progress. Developer has to update time spent on each ticket for the day (8hrs per day, 40Hrs per week) such that we can have track of ticket

• Make sure Sonarlint setup is done in your IDE and make sure it is working fine.

• For any impex related changes, do not copy paste from older impexes as those details might have outdated in later releases. In the impexes, add the attributes which is supposed to change as part of your current story. Have extra care on introducing new changes to solrindexedproperties/facets and webservice operations related item types.

• Once development is done, raise PR and assign to the respective lead. If a second round of review is needed, leads should assign to architect side. Once PR is approved, assign to the merger/release management lead for the merging activity.

Hope this step, help in formulating the development to review process which should be followed in general for SAP Hybris/ SAP Commerce Cloud development of stories.