Tool Features

Dashboard

It gives you a bird’s eye view of your entire project – at a glance you can make out how well your team is performing, how much development has taken place till date, what the team is currently doing and how well iterations and the project is proceeding.

FEATURES

Velocity chart

The Velocity chart displays the amount of business value delivered in the form of user stories in each sprint. It helps you to predict how much work the team is capable of doing and can get done in future sprints.

Burndown chart

The Burndown chart shows how quickly the team is developing user stories. It plots the total team effort versus the amount of work delivered in each sprint iteration.

Task summary

Task summary displays the total number of tasks allotted to each resource, how many of them are pending, how many are completed, how many are currently in progress and how many of them have been completed. You can also view the status of each task allotted to each team member.

Resource workload

The Resource workload exhibits the availability of each resource in terms of working hours for a sprint. It displays the time slots of resources in an iteration - how much work in terms of working hours has been taken up by each team member, how many hours of work has been spent in the current sprint and whether a team member is overloaded with work or not.

Activity log

The Activity log narrates all the work related activities performed by the team members in the current sprint.

User story summary

The User story summary displays a synopsis of all the stories created in the sprint. You can get a bird’s eye view of the total number of stories created in the sprint, how many stories are pending, how many developed stories got accepted and how many of them were rejected.

How is the dashboard feature useful?

One of the most important and useful of all Scrum tool features the dashboard given you an overall picture about how your team is performing and how much of work has been carried out in the project. An important information radiator, the dashboard exhibits the velocity chart which plots the speed at which the development team is completing user stories over time. The burndown chart is a clear indicator about the extent of work done and how much of it is still remaining. The activity log records the activities of developers, designers, testers and other team members. It is used to monitor the project and make informed decisions based upon the real-time data it collects from various activity sources.

Want to know more about Agile?

If you’re new to Agile you can join our Agile training programme for free – We’ll help you get started with the tool and Agile implementation!

Product Backlog

It constitutes the list of all things needed to complete the project. Each list item, also known as a product backlog item "PBI" taps the value of each product feature in the project. The feature supports the creation and maintenance of user stories or PBIs and detailing them with important information such as acceptance criteria, story description, estimation, etc.

FEATURES

Detailed user story planning and management

Create and edit user stories and fill in acceptance criteria and other related details. Also attach image and document files to properly explain or clarify the story. Link developers or other resources to task using drag-and-drop features. You can also estimate the time in which the developer plans to complete his/her work.

Prioritize user stories using drag-and-drop features

Sort or arrange product backlog items or user stories based upon their importance or business value in the project. Pick, drag, rearrange and release stories using dynamic drag-and-drop features.

Epic management

Effectively manage large user stories or epics by breaking them into a number of smaller and easily developable user stories or tasks. You can create an epic, define issues or points in them, and later close the epic once it’s decomposed into highly grained stories and tasks.

Tagging of user stories

Mark user stories as defects, bugs, research, etc. on the basis of their nature and functionality.

Advanced search features

Search or filter user stories on several types of search criteria such as user story description, the resource associated with the story, type of story, etc.

What is the importance of Product Backlog?

It is a prioritized list of work i.e. all functional and non-functional requirements in the project, in the form of user stories, that the team selects and develops as per the project’s roadmap and plan. All work items needed to complete the project i.e. user stories, design changes, bugs, customer requests, technical debt, actionable items from retrospective sessions, etc. constitute the backlog. Ideally, all important backlog items are arranged on the top followed by less important ones in the middle. The items having the least value remain at the bottom of the backlog list. The backlog serves as a base for sprint or iteration planning. It is important because:

  • The entire project value is contained in the product backlog.
  • Each product backlog item adds a certain value for the customer.
  • All items in the backlog are prioritized or ordered as per their business value or importance.
  • Product backlog items should be properly detailed and explained to get maximum value make work easy for the development team.
  • Items in the backlog should be properly estimated in terms of how difficult they are to develop.
  • The Scrum product backlog is a dynamic “living” artefact – it is changed and updated constantly by the team.

Want to create your own Product Backlog?

If you’re new to Agile and Kanban you can join our Agile training programme for free – We’ll help you get started with the tool and Agile implementation!

Defect Backlog

The defect tracking feature helps to easily track, record and manage all bugs and defects in the project. Team members can collaborate, plan and prioritize how to resolve defects using the tool feature.

FEATURES

Defect story planning and management

Manage defect stories and update them with new acceptance criteria and other details. Attach image and document files to properly explain or clarify the defect. Link developers or other resources to defects using drag-and-drop features. Categories defects based upon their severity and occurrence.

Filter defects on various parameters

Sort or view defects based upon their cause or occurrence i.e. view defects that are design related, code related, functionality related, etc

View defects using list and grid views

Preview defect stories using a simple list format or get a consolidated view using the grid format.

Resource workload

The Resource workload exhibits the availability of each resource in terms of working hours for a sprint. It displays the time slots of resources in an iteration - how much work in terms of working hours has been taken up by each team member, how many hours of work has been spent in the current sprint and whether a team member is overloaded with work or not.

Advanced search

Search or filter defect stories on several types of parameters such as defect’s description, the resource associated to resolve the defect, type and nature of defect, etc.

Specify the source of each defect

Link the origin of the defect, or the parent user story in which the defect has occurred with the actual defect story.

Tag defect stories

Flag or mark defect stories based upon their severity and occurrence.

Prioritize defects

Reorder or arrange defects as per their importance or resolution plan.

Why is the Defect Backlog important?

A defect is a bug, or an error, failure, flaw, or fault in a particular feature or functionality which leads to unexpected or incorrect results. Fixing a defect found after the deployment of a product feature is far more expensive in terms of cost and efforts as compared to identifying and fixing it earlier, or even during the development stage. The defect backlog feature helps to mark and track defects identified during the testing process, or even a later stage after it is shipped (though ideally bug and defect free features should be developed by the team). It is very important to identify defects and manage them effectively to reduce technical debt from accumulating. The defect backlog tool feature helps the product owner and the team easily manage and resolve defects in the project.

Want to learn how to reduce defects?

If you’re new to Agile and Kanban you can join our Agile training programme for free – We’ll help you get started with the tool and Agile implementation!

Release Planning

Create high-level business value generation plans in the form of releases to decide what features need to be developed at what time so meaningful and profitable value in the project can be delivered to the client on consistent basis.

FEATURES

Release wise backlog

Filter and view the entire product backlog for a particular release. You can select different releases planned in the project and view what stories have been assigned to them.

Set release milestone dates

Specify the completion dates for each release in the project.

Plan multiple releases

Work upon more than one release at a time.

Burn up chart

Track the project completion status i.e. how much of work has already been completed by the team in a project. The ideal line or the project scope line signifies the ideal rate of work the team members should target and try to complete while the completed line indicates the actual rate at which the team is working and delivering productivity in the project.

Burn down chart

Same as a Burn up chart but instead of indicating how much of work has been completed in the project, the chart focuses upon the total amount of work still remaining in the project.

How is release planning feature useful?

The goal of planning a release is to estimate which features should be delivered within a release deadline - if the release deadline is fixed - or to decide a tentative delivery date within which a given set of features should be developed. The idea is to plan the project in a way such that enough ROI is generated so the project can pay itself off and still generate a decent profit.

  • It gives a common vision to the entire team regarding what needs to be achieved and when.
  • It facilitates the team in making informed decisions and detailing work during Scrum ceremonies.
  • It gives a clear idea to the team how to prioritize user stories.
  • It aids in resolving conflicts and guides the team in achieving a correct balance during trade-offs or negotiating the development of user stories with the client or stakeholders.

Want to know more about effective release planning?

If you’re new to Agile you can join our Agile training programme for free – We’ll help you get started with the tool and Agile implementation!

Sprint Planning

Plan single or multiple sprints by selecting user stories from the product release backlog. Drag-and-drop stories and estimate them, sort or rearrange the stories in the backlog, update story details and create your sprint backlog.

FEATURES

Plan single or multiple sprints

Design or plan a single or multiple sprints with one or more Agile teams. Use drag-and-drop features to move user stories from the release backlog to sprint backlogs and reorder/prioritize them as per their importance or business values.

Allocate resources to stories and tasks

Assign work to individual team members based upon their work load and availability. Find how many tasks are assigned to individuals and how much work they’ve currently taken up in terms of working hours. Dynamically associate members to tasks using drag-and-drop features.

Acceptance status

Define the acceptance criteria for a user story.

Start and complete sprint

Close any currently active sprint and start or activate a new one.

Add or remove backlog items

Insert new user stories or product backlog items without leaving the page. Update user story details on-the-go and even delete backlog items.

Categorize user story

Mark user stories as defects, bugs, research, etc. based upon the nature and functionality of story.

How is sprint planning feature useful?

The Sprint Planning meeting, also known as an Iteration meeting, helps the team members to plan work and agree upon how much work in the form of user stories or backlog items they can confidently complete during the sprint iteration. In addition, the team members can decompose stories into individually developable tasks and specify the acceptance criteria, DoD and other missing criteria if required. The delivery of business value in the project is planned during sprint planning sessions.

Want to know more about effective sprint planning?

If you’re new to Agile you can join our Agile training programme for free – We’ll help you get started with the tool and Agile implementation!

Timesheet

It lets you sort and view data pertaining to the daily work carried out by the resources.

FEATURES

View timesheet date wise

Preview the productivity levels of resources sorted date wise.

View timesheet task wise

Preview the productivity levels of resources linked to a particular task, or sort the data tasks wise.

View timesheet resource wise

Preview the productivity levels data of a particular resource, or sort the data resource wise.

Export data to Microsoft Excel

Transport the team’s productivity and timesheet related data into Microsoft Excel format.

Advanced search

Search or filter tasks on several types of search criteria such as user story description, the resource associated with the story, type of story, etc.

Why is the Timesheet important?

In Agile productivity can be measured using certain metrics:

Efficiency

How much quantity and quality of value (work) is delivered to the customer on consistent basis.

Collaboration

Teams can be geographically collocated or remotely placed. However, Scrum principles suggest teams and team members should share ideas and find the best possible ways of completing work without compromising upon quality aspects. This is possible only if teams collaborate in an effective manner.

Effectiveness

Features developed by the team should be monetizable and fetch ROI for the organization. The work done by the team should contain a certain business value and it depends upon the team how to focus upon the business value and generate it.

Quality

The quality eventually decides how well the product will perform in the market. Quality aspects can be achieved by improving code quality, testing the code properly using reliable testing methods, following continuous integration practices, etc.

The timesheet features helps the management to determine how well the team is achieving these parameters. The work related data along with the efforts put in by the team is recorded by the timesheet feature. The management can study the timesheet feature to make informed decisions.

Want to increase team productivity?

If you’re new to Agile and Kanban you can join our Agile training programme for free – We’ll help you get started with the tool and Agile implementation!

Scrumboard

It provides a visualization of the entire development flow and the current status of each task in the sprint. You can focus upon the status of each backlog items and monitor the work assigned to each team member. It summarizes the total amount of work completed as well as remaining in the current sprint.

FEATURES

Visualize the work in progress

Find what tasks are currently being developed, who is developing them, how much of work has been completed, and how much of it is still pending. Also get to know which resources are currently engaged with the tasks.

Customizable columns/lanes

Configure the board columns as per unique client and team requirements.

Easily update task status

Just drag-and-drop tasks from “To Do” column to “In Progress” and “Completed” columns as the story develops.

Collaboration

Share data in the form of documents, images, and files with team members.

Identify and mark defects

Mark user stories as defects. Defects have to be resolved on a priority basis to reduce waste. Stories and tasks marked as defects are of immediate concern to product owners and clients.

Team wise scrum board

View individual scrum boards for each team in the project.

How is the scrum board feature useful?

The scrum board functions as a collaboration hub where all team members can record their activities and keep each other updated regarding what and how much of work has been completed till time. It is usually split up into three columns - "To Do", "In Progress" and "Done" - and functions as a placeholder for sticking on electronic Scrum story cards or index cards. A card exists for each task decided by the team during the sprint planning session, and as team members start developing tasks, the board is updated in real-time to reflect the changes. It can be useful in the daily stand up sessions to remind the team about pending work in the current sprint and to motivate them for increasing productivity levels. The task board is "reset" at the beginning of each sprint or iteration.

Want to know more about Agile?

If you’re new to Agile you can join our Agile training programme for free – We’ll help you get started with the tool and Agile implementation!

Kanban Board

It is used to visualize and optimize the flow of development stories, or work, amongst the team. The Kanban board gives you full visibility into what’s next in the development pipeline so when one task is completed the team can quickly move on to the next one.

FEATURES

Detailed user story cards

The feature supports all essential details for each user story while it displays only the most important ones on the board itself. You can edit details and slip up stories into tasks. View stories as issues, bugs or tasks. Click on a story to get all relevant details including priority, comments, attachments and much more.

Configurable lanes or columns

Configure individual columns as To Do, In Progress, Completed, etc. You can create additional columns as per your user story development work flow and name them accordingly.

Customization of work flow

You can define or create your Kanban board exactly as per your specific workflow based upon your client-centric or business related requirements. You can customize the board as your team or business process grows.

How is the Kanban board useful?

Agile software development teams try to implement Lean-Agile principles by matching the amount of work in progress “WIP” to the team’s actual capacity of doing work. The team can get more flexibility while planning work, create more business value in the form of successfully developed stories and increase team velocity through improved collaboration. The team develops only one story at a time and focuses upon work that's currently active or in progress. Once a user story or a work item is completed, another one is picked up from the top of the backlog and the team starts working upon it. The product owner can freely prioritize work without disturbing the team since changes carried out in the product backlog stories don't impact the team's work.

Want to know more about Kanban?

If you’re new to Agile and Kanban you can join our Agile training programme for free – We’ll help you get started with the tool and Agile implementation!

Reports

Get valuable reports explaining the current velocity of the team, actual efforts spent against efforts planned, sprint status, project summary and many other important reports to help in project, sprint and release planning.

FEATURES

Velocity Chart

Display the rate and the total amount of work delivered by a team in each sprint.

Sprint Effort Variance

Displays a comparison of the total efforts planned vs. actual efforts put in in "Spent Hours" in a sprint.

Project Summary

See a detailed view of all projects defined at company level - Project start date, end date, project status etc.

Sprint Health

Report shows how well a team, or a resource, has performed on a daily basis in a sprint.

Sprint Summary

This report offers a brief view/summary of all sprints in the project.

Acceptance Criteria Rejection Report

Get a detailed view of all acceptance criteria listed in the project and how many of them have been rejected.

Defect Report

Get a detailed view of all defects existing in the project.

Work In Progress

Get a detailed view of all tasks defined in the sprint and how many of them are in progress.

Why are the reports important?

Agile metrics available through the tool reports assist product owner and the team to plan further work.

Provides statistics for further planning

Releases and sprints are planned keeping in mind various metrics such as velocity, sprint health, burn down efforts etc. which are available through the reports.

Team assessment

The team’s performance has a direct impact upon the project deliverables. The reports help to assess how the team is performing, what its productivity levels are, and how soon the team can complete the project.

Delivery of business value

Scrum ensures that the project’s business value is delivered to the client, stakeholders or investors on a regular basis. Determine and plan how much and how soon business value of product features can be delivered, and in what manner.

Metrics in Agile provide reliable and highly useful indications regarding the team’s progress and productivity levels in a project. By knowing the metrics, the team can assess its progress and decide which areas to focus upon and what tasks to prioritize. It’s easier to adapt to changes when the team’s capacity to handle changes is known beforehand. In addition, Agile metrics help stakeholders and investors to get a good idea how their project is proceeding and what more needs to be done to complete the project successfully.

Want to increase team productivity?

If you’re new to Agile and Kanban you can join our Agile training programme for free – We’ll help you get started with the tool and Agile implementation!

Discussion Board

Proper and effective collaboration is a must if projects are to be completed in a streamlined manner. Healthy and meaningful discussions lead to successful resolution of issues and problems. Most teams find it difficult to collaborate because they don't have a proper venue to discuss thoughts and ideas. Secondly, a project may involve discussions upon several topics and teams may find it frustrating to filter out useful conversations from a pool of posts dumped in a haphazard manner in a common repository.

The Discussion Board feature helps teams to organize discussion into topics, and invite selected members for each discussion so only concerned members end up receiving updates regarding topics they're involved and interested in. This helps teams to stay focused upon specific topics and issues. Moreover, invitees to the discussion can maintain and keep track of notes and discussion points so they can get a clear picture how the particular discussion has evolved, what other team members think, and what kind of resolutions they're interested in. You can also share presentations and data files with the team to explain your view points and ideas.

The feature is very essential for distributed teams since they can benefit by reading offline messages and receive discussion points even when the client and other team members are not available due to differences in time zones.

FEATURES

Add or create a new discussion

Set up a new discussion point in the dashboard by describing what the discussion is about and give a name to the topic.

Select and invite members to the discussion group

Choose team members and invite them to the discussion by sending them joining request in their email IDs. Helps to create virtual sub-teams involved with specific tasks or work related issues.

Share files with group members

Collaborate with others by sharing files, ideas, presentations, slides, etc. and receive feedback from them. Find what they have to say about your ideas to carry forward the discussion.

Send notifications to members

Send discussion updates to only those members who wish to receive them real time. Very useful to distributed teams since team members can get reminders about what discussions took place and what was decided in their absence while they’re offline or not available due to time zone differences.

File Manager

The File Management feature offers a graphical user interface “GUI” for accessing and displaying all files created in a project at any given instance of time. It helps in managing files – copying, moving, opening, deleting and searching for specific files - and categorizing them into groups or directories as per choice. The browsable navigation system lets the user move easily through the file hierarchy and locate the level where files are stored or arranged. Its purpose is to make file handling easier so important files can be accessed quickly by the users.

FEATURES

Add or upload a file

A file can be attached directly in a User Story, Task and Discussion board. Another way of adding a file into the project is to upload it directly from the PC or cloud using the upload or add file feature by clicking the mouse in the whitespace area in the Details panel on the right, or alternately clicking on the upload file icon in the panels header portion.

Move a file from one location or directory to another

A file can be moved anywhere in the Details panel using drag and drop features. To relocate a file from one directory level to another use the Move file feature by clicking on the icon in the panels header. You need to specify a destination location or folder as a target.

Delete a file or folder

Select the particular file or directory in the Details panel and click on the Delete icon in Panels header. To delete multiple files or folders use the (Ctrl) key.

Download or export files or folders

To export or download project related data in the form of files, select the required files or folders from the Details panel and click on the Download icon in panels header. Multiple files and folders can also be selected for download using (Ctrl) key. Data is exported/downloaded in a .ZIP file format.

Create folder

Create a new folder by selecting the Create Folder icon in the panels header. New folders are created to structure and organize your data in the project.

Team Review

The sprint review or the team review meeting is held at the end of each sprint. In the meeting, the team demonstrates all completed stories whose Definition of Done has been met during the sprint. Typically, work is demonstrated in the form of a "demo" explaining the functionality of new features. User stories or work not completed during the sprint is not included in the demo. All pending or rejected work (user stories) is/are re-estimated and put back in the product backlog. The team review event is kept informal.

The Team Review feature helps to create a list of review points to summarize the sprint review event. It is very simple to use. Generally individual review points are created for each user story. You can also note down points to create new user stories for future sprints.

FEATURES

Sprint selection

Select a sprint from the drop down list to review it. Only current sprints can be selected for the review.

Current velocity

Displays the team velocity of the sprint selected.

Completed stories

Total number of user stories completed during the sprint.

Accepted stories

All shippable stories and work properly completed in the sprint.

Rejected stories

Work not fulfilling the DoD and/or acceptance criteria and rejected by the client or product owner.

Burndown chart

Displays the rate at which work was completed by the team during the sprint. It explains the total team effort versus the amount of work delivered in each sprint iteration.

Review points

Add review points to summarize the work taken up (user stories and tasks) by the team during the sprint.

Team Retrospection

Since there is always a scope of improvement for the team, it should constantly think about opportunities where it can improve its velocity and deliverables. A short duration of time, at the end of each sprint, should be set aside to reflect upon how well the team is doing, where it can improve, and what activities should be continued or stopped to generate more business value from future sprints. The sprint review event is held so the team can do self-evaluation, self-correction and organize itself to perform better in the future.

The team should try to identify activities which it should:

  • Start doing
  • Stop doing
  • Continue doing

Teams often also discuss:

  • What went well in the Sprint?
  • What could be improved?
  • What will we commit to improve in the next Sprint?

The Team Review feature helps to capture the three courses of action i.e. to identify areas of improvement, what activities should be stopped and what activities the team should continue doing. In addition, you can also create a list of actionable items which can be assigned to specific team members and even converted to user stories later on.

FEATURES

Sprint selection

Select a sprint from the drop down list to review it. Only current sprints can be selected for the review.

Current velocity

Displays the team velocity of the selected sprint.

Completed stories

Total number of user stories completed during the sprint.

Accepted stories

All shippable stories and work properly completed in the selected sprint.

Rejected stories

Work not fulfilling the DoD and/or acceptance criteria and rejected by the client or product owner.

Burndown chart

Displays the rate at which work was completed by the team during the sprint. It explains the total team effort versus the amount of work delivered in each sprint iteration.

Improvement

The areas of team improvement. Each area where the team can improve its working is stated as a point. The team should closely focus upon the improvement areas.

Stop doing

Non-productive activities that should be stopped immediately by the team. All actions by the team that do not yield positive outcomes and activities that are counterproductive or harmful to the team and its further growth should be stated as "Stop doing" points.

Continue

Activities or actions that help the team to improve its performance, increase its velocity or help to enhance the delivery of business value at the end of the sprint should be stated as "Continue" doing points.

Actions

Create a list of actionable items at the end of sprint retrospection event. Typically, this is a call-to-action type of list created for follow up reasons so the team can take corrective or improvement measures discussed during sprint retrospection. A team member can be selected from the drop down list to do the follow up activity or work. Moreover, a call-to-action can also be converted to a user story if required.

Stand Up Board

The daily scrum is a 15-minutes time-boxed event in which the development team synchronizes its activities and creates a work plan for the next 24 hours (one working day). The work done by the team since the last daily scrum meeting is inspected during the meeting, and the team also decides what and how much work it plans to do in the coming 24 hours (the current working day, or "today"). The event is usually held in the same place and at the same time.

The objective is to inspect how the team is achieving the sprint goal and ensure that the work taken up in the sprint backlog is fulfilled in time. The team makes effort to self-organize itself and collaborate to accomplish the sprint goal.

The daily standup or scrum meeting should not be used as a problem solving or issue-resolution meeting. Its purpose is to track whether the team is streamlined in its daily work and identify any pitfalls faced by the team members. Each team member updates the entire team with his/her work by answering the following three questions:

  • What did you do yesterday?
  • What will you do today?
  • Are there any impediments in your way?

The team gains a very good understanding towards the total work completed in the sprint, how much of it is still remaining and what team member is working upon which task.

The feature helps to log the daily standup event and note down any impediments faced by the team. Team members can be assigned to resolve the impediments, and if required a new user story can be created out of the impediment to tackle the issue at a later date in forthcoming sprints. The excellent part of the feature is that it offers a timer to time box the standup event and the team can gain valuable insights into its current progress using the velocity, team wise summary and resource wise summary features.

FEATURES

Team selection

Select a team from the drop down list whose daily standup session is to be logged. The feature is useful when multiple teams are working on the same or different projects.

Sprint selection

Choose a sprint from the drop down list as per the team selected. Only current sprints can be selected for logging purpose.

Sprint day

Since a sprint extends for several days, it’s important to select the particular sprint day so observations can be logged for that day.

Start timer

It’s very important to keep the daily standup event time boxed to 15 minutes. The timer reminds the team members to remain very brief while explaining the work done by them and make sure no member utilizes more time other than the time duration allotted to him/her.

Impediments

Issues or problems hampering team productivity and preventing team members from doing their work can be stated as impediments. A unique person/team member can be assigned the task of resolving an impediment, and a date can be specified to ascertain the duration within which the resolution is needed. Subsequently, an impediment can also be converted to a user story so it can be resolved in forthcoming sprints. In such cases, the impediment user story is transferred to the product backlog. Once an impediment is resolved it can be deleted from the board.

Team summary

An overview of the current sprint status with regards to how much of work is completed in the sprint and how much of it is still pending. Also know the current velocity at which the team is working and how fast it needs to speed up its work to meet the sprint goal.

  • Assigned

    Total number of stories assigned currently to team members in the sprint.

  • Completed

    Work in the form of user stories and tasks completed by the team in the current sprint.

  • Actual work remaining

    Pending work i.e. stories which are unfinished (ongoing development work), and stories which are still to be developed (pending stories) can be known from the actual work remaining.

  • Team velocity

    The cumulative velocity, or the speed at which the entire team is collectively doing work is indicated by the team velocity parameter.

  • Required velocity

    Often teams need to speed up work so it can achieve the sprint gaol in time. The rate, or the speed at which the team is required to do work so it can deliver all work remaining in the sprint so far is indicated by required velocity.

Resource summary

A summary of the resource’s work status in terms of how much of work is completed by the resource in the sprint, and how much of work is still left pending. Also know about the current velocity at which the particular resource is completing his/her work, and how fast he/she needs to speed up work to complete all stories/tasks taken up for development in the sprint.

  • Resource name

    Name of the team member.

  • Assigned

    Total number of stories assigned to the resource in the current sprint and total time to complete the tasks. Know how many hours of total work has been given to the resource.

  • Completed

    Total number of stories completed by the resource in the current sprint and how many hours the resource has utilized to complete the work. Know how many hours of total work has been completed.

  • Left to do

    Total number of stories remaining to be done by the resource in the current sprint. How much of time the resource will take to complete the tasks. Know how many hours of total work is still pending in the sprint.

  • Current velocity

    The velocity, or the rate/speed at which the resource is currently completing work (stories and tasks) can be known by the team velocity parameter.

  • Required velocity

    At times developers have to speed up work so they can complete their tasks in time. The rate, or the speed at which the particular resource is required to work so he/she can complete and deliver all work taken up by him/her in the sprint is indicated by the required velocity parameter.

  • Mark as absent

    For attendance purpose – mark a team member as absent when he/she is on leave.

  • View more

    Find additional work related information about the resource. Find out what and how much of work has been completed and logged by the resource in the sprint. Also know what work was assigned and how many stories are still left pending as on date.

Comment Notifications

Collaboration is very important when several teams work together on a single or multiple projects. Team members need to be informed about what new activities have taken place and who has originated/requested them. People can offer valuable suggestions helpful to the entire team when they’re updated about new work or changes carried out in existing functionality. The comment notification features provides instant notifications to users or members included in the project whenever a user story or a task is commented upon.

The feature is useful to send notifications to the team members as and when some user story related activity is done in the project and everyone is required to be notified about it.

FEATURES

Resource name

Name of the team member or resource who commented.

Date

Date and time when the comment was made.

Project

Name of the project for which the comment was originated.

Task code

For which task the comment was made.

User story ID

The unique reference or ID of the user story in which the comment was made.

Message details

Actual details or particulars pertaining to the comment.

Help Desk

Client requirements form the base of all software development activities. There are many ways requirements can be captured and stored in a project. To cut down upon operational overheads, it is very important to make the best use of available talent and utilize resources in a proper manner. Process automation helps organizations to replace processes requiring manual intervention with automated processes that carry out targeted activities.

It can become very easy if your requirements can be sent in the form of emails and an automated process can convert those requirements into user stories in the project. The Help Desk feature does exactly that. Requirements sent by the client in the form of emails can be transformed into user stories by setting up your QuickScrum email handler feature to interface with your email account. All emails sent are converted automatically into user stories. You can configure the automation to automatically assign stories to a fixed project, or alternately prompt the admin to specify which project the user story should go into.

FEATURES

Ticket Code

Unique ID for the requirement sent by the client or customer.

Name

Name of the requirement. The user story created from the email has the same description as the name given to the requirement.

Project Assignment

Project within which the user story is to be assigned. When "Help Desk" option is used, the project name is selected from the drop down box.

Created Date

Date and time when user story is created in the system.

US Code

The unique code assigned to the user story when it is created automatically.

Customer Name

Name of the person who has originated the user story by sending the email.

GitLab

Git has completely changed how developers work. Since it provides a centralized, cloud-based location to share, store, test, publish, and collaborate with other developers, web development has now become quicker, reliable and more controllable in terms of meeting project deadlines. Version controlling helps developers to maintain track changes, revert back to older versions while bug testing and commit code changes when a piece of functionality is tested successfully. Moreover, the client and stakeholders get a chance to participate in test runs and provide valuable feedback regarding features development and the business value delivered.

The GitLab feature helps developers and designers in the project to create and share code easily and instantly using a shared repository. Ideal for IT and software development companies, organizations can now deliver valuable working functionality on time, and in the manner as desired by the client using GitLab features.

FEATURES

Project selection

The project needs to be created on GitLab first. Once it is created, it needs to be set up to work with QuickScrum GitLab feature. GitLab integration can be made active by selecting the project and marking it as “Active”

Create a branch

Define a line of development, or a branch in GitLab by stating the name of the functionality or feature the team is going to develop or work upon.

Remove a branch

Once a feature is developed and its code is committed (merged) to the repository, the particular line or branch is no longer needed on GitLab. To avoid overloading the repository with redundant resources and objects, the particular branch can be deleted and the space freed.

Merge requests

Most important from development point of view, once the code is developed and finally tested by the team, the versions created by individual team members have to be synced together using a “merge” request. A unique code containing all the work done by individual developers is thus created. This code is also the final code for feature functionality.

Commit list

Each updated version of the code, or “commit”, is stored with a unique reference number, parent object, author, date and other related details. As new code versions get developed, a unique “commit” is created for each update or version. The commit list can be viewed and appropriate actions taken.