• title Development Sprints

    Tracking Development Processes on JIRA

    banner svg

    Once the Sprint Planning is done, we dive headlong into the development and testing process. And we do that in the JIRA Agile swimlanes we define for the sprint. JIRA Agile, the project management tool we use at Srijan, defines a swimlane to be a "means of categorizing issues so that agile teams can see which issues they should work on next.”

    We primarily work with five swimlanes for a sprint. They are:

    To Do: This contains the backlog of all issues or tickets being tackled in the sprint. Developers in the team pick the tickets they are working on and move it to the next swimlane, In Progress.

    In Progress: In this swimlane, all members are able to view which the tickets are being worked upon, and by whom.

    To Verify: Once the developer completes a task, he or she can move it to this lane. This swimlane acts as the backlog of tasks for the tester.

    In Testing: A tester can pick a task from the To Verify swimlane and move it to this lane. Once the testing is completed as per the test cases defined, the ticket is moved to the Done swimlane.

    The are certain quality contamination issues that might arise at this stage, but our teams know how to find their way around those.

    Done: This is the swimlane for the Product Owner from the client team to start testing the features. To make it simpler for the PO to test the features, Srijan creates a Demo Script, a document that captures the process for testing in plain English. This ensures that POs can quickly conduct the tests and check whether the features have been developed in the right way. Using the Demo Script, the PO tests the features developed. If the PO considers a ticket to have been developed satisfactorily, he or she can close it. If not, it is sent back to the To-Do list. The PO doesn’t have to wait till the end of the sprint to start the testing. He/she can start it as soon as ticket is moved to the Done swimlane, which could be as early as the second day in the sprint. A task or issue can be closed only by the PO or the Scrum Master.

    In our Agile development services, everyone in the client’s product team has access to the sprint, and they can see for themselves how the development is progressing on a real time basis. For the ease of the management team, we send out a Single View Status Report, so roadblocks and risks identified are communicated to enable timely interventions.