{"id":1671,"date":"2017-04-04T15:37:49","date_gmt":"2017-04-04T15:37:49","guid":{"rendered":"https:\/\/www.nimblework.com\/knowledge-base\/swiftscrum\/\/\/?page_id=1671"},"modified":"2022-07-14T10:33:03","modified_gmt":"2022-07-14T10:33:03","slug":"glossary","status":"publish","type":"page","link":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/glossary\/","title":{"rendered":"Glossary"},"content":{"rendered":"

Archived<\/strong> \u2013 Archive is the last stage in the life-cycle of a workitem in Nimble and contains completed cards (User Stories\/ Defects\/ Issues). This stage can\u2019t be modified. The lead\/ cycle time of a story is calculated when it is archived from the Execution board.<\/p>\n

Backlog<\/strong> \u2013 Backlog is a notional placeholder\/ view which shows the consolidated list of workitems ( User Stories\/ Defects\/ Issues) that are to be worked upon. \u00a0One can search through the Backlog and add cards to the Execution Board.<\/p>\n

Blocked<\/strong> \u2013 Blocked is an indicator on the board that there is a problem at hand, which needs entire team\u2019s attention. When the card is marked as blocked, a red \u2018Blocked\u2019 tag appears on the card, which is easily visible on the board. While blocking, one needs to enter the reason which the card is being blocked. Once a card is blocked, it can\u2019t be moved until the blockage is resolved.<\/p>\n

Blocked Time<\/strong>\u00a0\u2013 This is the duration that the card was in a blocked state on the Execution board.<\/p>\n

Card<\/strong> \u2013 A card in Nimble can be a User Story\/ Defect or an Issue and represents a piece of work to be done.<\/p>\n

Cumulative Flow Diagram ( CFD)<\/strong>\u00a0\u2013 CFD diagram shows the count of cards in a particular state\/ lane for each day between a specified duration.<\/p>\n

Cycle Time<\/strong> \u2013 Cycle time in Nimble is computed as the time it takes for a card to move from the first lane of the Execution\u00a0Board (Typically termed \u2018Ready\u2019 ) to the archived state. \u00a0It represents the time a bug\/ feature took to get completed, from the time it was prioritized.<\/p>\n

Control Charts<\/strong> \u2013 Control charts display limits and which is the voice of the process. Points outside of these control limits are signals indicating that the process is not operating as consistently as possible; that some assignable cause has resulted in a change in the process. Similarly, runs of points on one side of the average line should also be interpreted as a signal of some change in the process. When such signals exist, action should be taken to identify and eliminate them. When no such signals are present, no changes to the process control variables (i.e. \u201ctampering\u201d) are necessary or desirable.<\/p>\n

Analytics<\/strong> \u2013 Analytics is the landing screen that you see when you log in to Nimble. \u00a0It can be personalized by adding an array of widgets available in the \u2018Add Widget\u2019 view.<\/p>\n

Lead Time<\/strong> \u2013 Lead time in Nimble is computed as the time it takes for a card to move from the backlog state to the archived state i.e. the time when the card was created to when it was archived. \u00a0It represents the total time a bug\/ feature took to get completed, including the waiting time in the backlog.<\/p>\n

Owner<\/strong> \u2013 A Story\/ Defect or Issue\u2019s owner is the person who\u2019s currently assigned to it. \u00a0Anyone who \u201cpulls\u201d a card from the backlog or any waiting lane and moves to working lane becomes the owner of the card in that lane.<\/p>\n

Board<\/strong>\u2013 Work can be organized in Nimble under boards. Within a board, you can create backlog items (User Stories\/ Defects\/ issues), invite people to work with you and set up your own Execution board.<\/p>\n

To-Dos<\/strong>\u2013 Each User Story in Nimble can be broken further into a list of To-Dos. One can mark the \u2018Current State\u2019 of to-do as \u2018Completed\u2019 once the task is over. As the to-dos for any user stories are completed, the % completion of the user story increases.<\/p>\n

Wait Time<\/strong> \u2013 Wait time in Nimble is computed as the time any card was lying idle in any column of type \u2018Completed and Waiting\u2019. It represents the time a defect\/ feature was waiting to be pulled from the previous queue.<\/p>\n

Work-In-Progress Limit<\/strong> \u2013 A Work-In-Progress (WIP) limit is the limit set of the number of cards that can be worked on at any one time, in any lane. This allows people to focus on what\u2019s important and not switch too much between tasks (which creates waste). WIP limits can be set by clicking on the \u2018Modify Process\u2019 link on the Execution board.<\/p>\n

Work Time<\/strong> \u2013 Work time in Nimble is computed as the time it takes for a card to move in and out of any column of type \u2018In progress\u2019. It represents the time a defect\/ feature was worked upon, in any of the columns.<\/p>\n","protected":false},"excerpt":{"rendered":"

Archived \u2013 Archive is the last stage in the life-cycle of a workitem in Nimble and contains completed cards (User Stories\/ Defects\/ Issues). This stage can\u2019t be modified. The lead\/ cycle time of a story is calculated when it is archived from the Execution board. Backlog \u2013 Backlog is a notional placeholder\/ view which shows […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"template-full-width-with-search.php","meta":{"footnotes":"","rating_form_position":"","rating_results_position":"","mr_structured_data_type":""},"multi-rating":{"mr_rating_results":[]},"_links":{"self":[{"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/pages\/1671"}],"collection":[{"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/comments?post=1671"}],"version-history":[{"count":11,"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/pages\/1671\/revisions"}],"predecessor-version":[{"id":10250,"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/pages\/1671\/revisions\/10250"}],"wp:attachment":[{"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/media?parent=1671"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}