This article covers how to add and manage workitems/cards in Nimble, along with the different workitem/card types.
|
Skip Ahead to: |
Common Steps to Add a Workitem on the Workitem Page
To add a workitem:
- Click the ADD button on the listing page of the workitem.
- Enter the details as explained below:
- Name: Enter a logical name for the workitem. The name should indicate what this workitem is about.
- Description: Enter a short description of the workitem. You can enter the information gathered from the customer in the everyday language.
- Priority: Specify the urgency of the activity. This could be high, medium, or low, depending on the urgency of the issue.
- Assigned to: Select the person responsible for completing the activity.
- Estimate Hours: Enter the estimated hours for the workitem.
- Due Date: Enter a due date for the workitem.
- Percent Complete: Specify the percentage of work completed for the activity (eg- 10%, 25%, 50%, 75%). Note: The fields may vary based on the workitem.
- Click the SAVE button.
Once the card is created, the following tabs become visible:
Common Operations to Manage a Card
- Edit
- Insert Rows
- Delete
- Export
- Import
- Copy
- Convert Card Type
- Sort
- Log Effort (available only for projects which have the ‘Include in Timesheet’ option enabled for the workitem).
Different Card Types in Nimble
Card Types in Nimble represent structured workitems used to plan, track, and manage various aspects of project execution—such as features, issues, and risks. They enable teams to streamline workflows, ensure traceability, and maintain clarity across all stages of delivery. The following is a comprehensive list of card types available in Nimble:
Activities
An Activity card is used to track routine operational or non-development tasks, such as documentation, meetings, follow-ups, or reviews. It helps maintain visibility into ongoing team efforts that support project health and collaboration. Navigation: Execute >> Activities
Change Requests
Change Requests are created by Product Managers or Business Analysts when new requirements arise, often due to customer needs. The Change Management process includes capturing the request, analyzing its impact, prioritizing, assigning resources, implementing the change, testing, reviewing, and finally closing the request. Navigation: Manage >> Change Request
Customers
You can seamlessly onboard a customer from the sales team to the customer success team by collecting all the key information that the sales team collects during the post-sales handoff meetings. It includes the expectations of the customer, the cost of onboarding, and the CSAT rating they intend to achieve by using the product. Note: This menu is only available for the Post Sales Handoff Template. Navigation: Execute >> Customers
Defects
A defect is a non-conformity observed against the specifications. Defects are logged as a part of the testing process, reported internally, or reported by customers. You can manage the entire life cycle of the defect through the automated process defined in your project, which includes reporting, verification, resolution, and closure. Configure the Defect Form to capture information on the defect identification stage, priority, and impact, to be able to take measures to prevent them early in the project. Navigation: Execute >> Defects
Digital Assets
Digital Assets help businesses store and manage all customer-related content—such as contracts, proposals, presentations, or marketing collateral—in one centralized location. This makes it easy to access, share, and reuse important files, improving collaboration and productivity. They also support marketing efforts by organizing e-books, whitepapers, or webinars to engage prospects, educate users, and convert them into loyal customers. Note: This menu is only available for the Digital Assets Management Template. Navigation: Execute >> Digital Assets
Epics
An Epic represents a large body of work that can be broken down into smaller user stories or tasks. It allows you to plan and track progress at a higher level of precision. Epics help structure multi-sprint initiatives and define large features or capabilities. Navigation: Execute >> Epics
Features
A feature is the function of the product that adds business value to it. It represents a collection of user stories. A chunk of functionality that delivers and evaluates considerable business value. Navigation: Execute >> Features
Issues
Issues can be unexpected behavior or potential problems in a product or software which may hamper the product quality or service. Issues can be raised internally, or by clients and customers, which are generally termed as ‘Tickets’ and need to be resolved. In the application, the Issue Management process includes logging identified issues, reviewing and analysing the impact, informing stakeholders, assigning resources, taking steps to resolve, reporting status, and closing issues. Navigation: Manage >> Issues
Job Applications
A Job Application allows you to plan and execute the recruitment of candidates until their joining. Collect and access candidate data and ensure that all the required data has been received. Manage your hiring process and communicate with your team. Note: This menu is only available for the Recruitment Template. Navigation: Execute >> Job Applications
Job Postings
A Job Posting is the first step in the recruitment process to track the job posts to be filled and monitor their progress. A job posting includes information about the position such as department, job location, working mode, job roles, responsibilities, etc. Note: This menu is only available for the Job Postings Template. Navigation: Execute >> Job Postings
Releases
Releases help you plan and create your releases and tag sprints to them. For each project, you can track the progress of each release separately. It helps teams organize and communicate long-term planning across iterations. Navigation: Plan >> Releases
Risks
Risks are potential events or situations that can impact your project objectives if they occur. Managing risks proactively helps teams anticipate uncertainties, minimize negative impacts, and stay on track to achieve project goals. Nimble provides a dedicated Risk card to identify, assess, and monitor risks throughout the project lifecycle. This article explains the rationale behind adding risks and how to manage them efficiently using Nimble. Navigation: Manage >> Risks
Sprints
Sprints form a part of a release as sprints are tagged to a specific release. Each Sprint is a subset of the final Release and is built on the functionality of the prior Sprint. It is a fixed time period where the team works on selected items such as user stories, tasks, or bugs. It helps teams deliver small parts of the project regularly and track how much they can complete in each cycle. Navigation: Plan >> Sprints
Team Goals
Set clear goals for the team – Create a plan, assign the goals to the team, and manage the work to achieve them. You can also prioritize work in line with the company’s goals to boost the team’s overall productivity and get effective results. Note: This menu is only available for the Team Goals and Objectives Template. Navigation: Execute >> Team Goals
Team Objectives
Set clear objectives for the team – Create a plan, assign the objectives to the team, and manage the work to achieve them. You can also prioritize work in line with the company’s objectives to boost the team’s overall productivity and get effective results. Note: This menu is only available for the Team Goals and Objectives Template. Navigation: Execute >> Team Objectives
Technical Stories
A technical story (also called a technical user story) is a form used to describe any work which is non-functional and technical in nature. The technical stories are created to improve the technical support of a system. One example of technical work is creating/changing back-end tables to develop a new function or improve the functionality of an existing function. Navigation: Execute >> Technical Stories
Themes
A Theme is a high-level strategic grouping used to organize related epics or features around a goal. Themes provide clarity at the portfolio level, helping teams prioritize and align work with organizational objectives. They help maintain long-term vision beyond individual tasks. Navigation: Execute >> Themes
Topics
The Topics workitem is used to organize knowledge or learning content into clearly defined subject areas. It helps manage curriculum outlines, onboarding content, or documentation groups. Topics can be linked to the Trainings, Test Cases, or Digital Assets to provide structured, searchable learning paths. Note: This menu is only available for the Content Planning Template. Navigation: Execute >> Topics
Training
Training workitem is used to plan, assign, and track training sessions or learning modules for individuals or teams. It can include session details, trainer info, target audience, duration, and feedback. This card helps ensure structured learning and team upskilling. Navigation: Manage >> Training
User Stories
User Story is a short and simple way to describe something a user wants to do in the system. It tells what the user needs, why they need it, and what benefit they get. A User Story is a software system requirement formulated by the customer, in one or two sentences, in the everyday language of the user. User stories are used for the specification of requirements (together with acceptance tests). Each user story is limited to ensure that it does not grow too large. Navigation: Execute >> User Stories
Videos
The Videos workitem is used to track the creation, review, publishing, or reuse of video content across projects. It captures information like video type, intended audience, production stage, and associated assets or campaigns. Note: This menu is only available for the Video Production Planning Template. Navigation: Execute >> Videos