Skip to content Skip to footer

Process Instructions Document

Daily stand up & Productive time sheets

Daily stand up needs to be submitted on the Slack following the specific format set for the standup.

The stand up should cover the list of tickets you worked on yesterday, the tickets you plan on working today and the hurdles or dependencies if you have any for completing your planned work for the day.

The tickets assigned to you on Jira/ TFS are marked with the priority as 1 through 4 or from highest to low. The tickets need to be picked up based on their priority. If you have multiple high priority/critical items on your name, you should discuss the list with your leader or the person guiding you through your work to decide the sequence of your tickets before starting the work.

Daily timesheets submission is mandatory using Jira/TFS logging for every ticket you work on throughout your day. Your timesheets should reflect at least 8 productive work hours.

Approach discussion mandatory

The process to be followed during development:

Approach Design & Discuss

  1. Design the development approach to be followed for the development task in hand.
  2. Explain, discuss and brainstorm the approach with the technical leader or Jayesh
  3. Make sure every scenario around the task is covered and addressed while designing the approach
  4. Document the development approach including class diagram, flowchart, future work scope, API documentation, etc wherever applicable.
  5. Start implementation only after approach finalization.


  1. Follow Object Oriented principles
  2. Conduct a thorough impact analysis before coding changes
  3. Proper, standard & meaningful class, method and variable names needed
  4. Complete unit testing from developer is mandatory before any ticket is delivered for QA
  5. The number of bugs encountered by a QA in your development work decide the quality of your work, impacting your performance, bonus and appraisals.
  6. Code comments required
  7. Follow the set branching process for creating new feature/fix branches, naming the branches, creating PRs after code completion, and for merging, updating and deleting the branches after merge.
  8. The list of branches needs to be maintained and updated at a central location by every developer for every repository.


Communication is of the utmost importance when working in a team. Communication does not only include the discussions with the teammates, but also involves the following aspects:

  1. Following Jira/TFS processes is mandatory
  2. Regular updates, comments on the tickets to convey progress
  3. Daily timesheet submission
  4. Constant communication with the team, including developers, QAs, leaders, etc
  5. Client communication whenever necessary
  6. Active responses, acknowledgements to messages, emails, or any communication channels that the team is following
  7. Proactive communication of any foreseen challenges, hurdles or even simple progress updates without the others having to follow up with you.

Performance Criteria

Performance measurements, bonus calculations and appraisals depend on the following aspects of your work.

  1. Communication – following communication guidelines described above
  2. The number of bugs encountered by a QA after development complete delivery of your task
  3. The timely, bug free delivery of your tasks
  4. Process following
  5. Taking accountability for your work

Was This Article Helpful?

1 Comment
  • 1. Analyze feature requirements
    2. Design high level approach. Block Diagram needed.
    3. Design low level approach. Class diagram needed.
    4. Review the approach to a reasonable level and start development.
    5. Any design challenges must be recognized and handled at the right time instead of letting design flaws percolate through next stages.
    6. Update the design diagrams.

Leave a comment

Your email address will not be published. Required fields are marked *

Close Bitnami banner