Agile Task Management

Software development is an agile process. It encompasses a series of activities or tasks spanning sequential stages -- planning and analysis, designing, implementation, testing and deployment/release. At each stage of the process, there are outputs produced and passed to the next stage for them to take further shape. For example, the designer produces a design blueprint and passes it to the developer for implementation. Upon completion, the tester steps in to perform testing for quailty assurance purposes and so on and so forth. As stages follow one another in order, we call it a development chain. This way of working ensures that the deliverables get worked on one aspect at a time. Not only does it help developers focus better on specific tasks in hand, it also provides an environment for the product to remain as stable as it can be throughout the development.

September 14, 2011
User Rating: / 0
Views: 1,210
PDF Link Link:	Add comments

A3 Platform is a tool that enables you to create tasks which are needed to meet a software requirement. After you set linkages and dependencies between these tasks you created, the tool helps you monitor the task progress and based on the rules you've already set, will alert the designated person that he or she can begin and continue with the work. This automation helps manage and progress through the development chain more smoothly. For example, the tool could automatically assign an implementation Task to a programmer when the design Task is done.

In this tutorial, we are going to form a development chain in A3 Platform to help manage meeting a system requirement of adding a register function. To do that, we are going to create some Tasks related to from designing the register page to deploying system with the new register function.

To try the example in this tutorial hands on, you must have A3 Platform installed on your computer. The following project and users will be used throughout this tutorial.

Project: Sample Project
Users:
1. Peter (Project Manager)
2. Roland (System Architect)
3. Mavis (Programmer)
4. Macy (Tester)

If you already have a running installation of A3 Platform, you may use your own project and users for this tutorial. Otherwise, please read the tutorial Download and Installation of A3 Platform to learn how to install A3 Platform and set up users and projects.

Creating Development Chain from UI Design to Deployment

Login as Peter.
Peter is going to create a Task for designing an user interface of the register page.

Open the Tasks view.
Create a Task by clicking on New Task.
Enter the Name of the Task: Design the Register screen
Enter the Details of the Task: Required fields: display name, login name, password
This is a design Task. Select its Location: 1.0 > I1 > Analysis & Design
Select Roland to be the Assignee, who is responsible for designing the register screen.
When the design of the register screen is finished, we can start the implementation task.

Here we are going to make use of the dependency feature to create the next task that will be initiated after completion of the screen design Task. Before we move on to creating another Task, we need to enable the related fields first. Click on the tiny button on the right hand side below the Details box, with an inverted triangle in it.
Check the checkboxes to show the Dependency and Depends On fields. Click OK at bottom right to confirm.
The fields Dependency and Depends On are now displayed. The Dependency field determines which Task is pending to be initiated and triggered by the completion/start/close of this Task. Contrary to Dependency, the Depends On field specifies which Task is being relied on by this Task for trigger. We will use the Dependency field only in this tutorial and we will talk in detail later on. Now, we want to create a Task for implementing the register function. Click on the inverted triangle button next to the Dependency field and select Task from the drop down menu.
This opens a new form for creating a new Task that is dependent on the screen design Task. Enter the name of the Task: Implement the Register function
The name is descriptive enough. Let's omit the details. Select Mavis to be the Assignee. She will be responsible for implementing the register function.
Click Save to return to the screen of designing Task.

The Dependency field is updated to show the newly created Task. Click on the drop down menu and select Complete to assign. A list of available options is displayed.
depend opts

The options are used to set rules to determine under what condition the dependent Task will be assigned/completed/closed. Here is a description of the available options:

Option	Description
Complete to assign	When the Status of this Task is set to Completed, assign the dependent Task.
Complete to complete	When the Status of this Task is set to Completed, set the dependent Task to Completed.
Complete to close	When the Status of this Task is set to Completed, set the dependent Task to Closed.
Start to assign	When the Progress of this Task is set to be between 0% to 100%, assign the dependent Task.
Start to complete	When the Progress of this Task is set to be between 0% to 100%, set the dependent Task to Completed.
Start to close	When the Progress of this Task is set to be between 0% to 100%, set the dependent Task to Closed.
Close to assign	When the Status of this Task is set to Closed, assign the dependent Task.
Close to complete	When the Status of this Task is set to Closed, set the dependent Task to Task.
Close to close	When the Status of this Task is set to Closed, set the dependent Task to Closed.

The default selection for Depends On is Complete to assign, which is fitting in this case, so let's keep it.
Click Save at bottom right to save this Task.
Let's continue creating other Tasks. Click on the link Implement the Register function in the Dependency field to open it.
Notice that at this moment, Mavis, the Assignee of the implementation Task, has not yet received notification of this Task because the design Task is not yet completed and the dependency is set to be Complete to assign. Let's create a Test Case to test the implementation.

Click Edit to edit this Task.
Create a dependent Test Case. This time, click on the inverted triangle at the Dependency field and select Test Case from the drop down menu.
In the popup window, enter the name of the test case: Test the Register function with correct data
Macy, a tester, is responsible for testing. Select Macy to be the Assignee.
Scroll down the window and enter the steps of testing the register function. We are not going to talk about testing here. If you want to know more about planning and performing testing, please read the tutorial Plan and Perform Testing.
Click Save to return to the implementation Task.
Same as before, we shall assign the test case to Macy when the function is implemented. Keep the relationship of dependency be Complete to assign. Click Save at bottom right.
Here comes the final Task in the development chain. After the function has been tested, we can deploy the system with the new function included for the end user to try.

Click on the link Test the Register function with correct data in the Dependency field to open it.
Click Edit to edit this Task. The Dependency field is hidden by default. Let's show it by following the steps described before. Click Edit to edit this Test Case.
Add a dependent Task.
Enter the name of the Task: Deploy System
Enter the details: Included function: Register
Set Peter to be the Assignee.
Click Save to return to the Test Case.
Click Save.