Explore topic-wise InterviewSolutions in .

Productivity is estimated in terms of CYCLE-TIME:

Cycle Time: It is the length of time to complete the PROCESS.

Throughput: It is the sum of the OUTPUT from a process in a given PERIOD of time.

Productivity is estimated in terms of cycle-time:

Cycle Time: It is the length of time to complete the process.

Throughput: It is the sum of the output from a process in a given period of time.

The benefits of Scrumban is:

• No NEED for upfront planning
• Involves team concept unlike Kanban
• It involves sprint and INCREASE the productivity of the team compare to Kanban
• No changes can be done to Sprint Backlog
• Product Owner can be involved in the team
• Daily Scrum- it helps the team to self-organize and self-manage
• Sprint REVIEW- it involves business STAKEHOLDERS, and they can give their FEEDBACKS
• It includes retrospective.

The benefits of Scrumban is:

Yes, it is possible through an open source solution known JimFlow, and it can INTERACT with Trac Tickets.

There are few benefits of it like:

• It PRINT tickets DIRECTLY out of the ticket system
• It supports flow boards having columns
• It can take photos in custom intervals
• With ticket title and type it can GENERATE digital version of the board
• Update ticket in ticket system on MOVEMENT.

Yes, it is possible through an open source solution known JimFlow, and it can interact with Trac Tickets.

There are few benefits of it like:

Kanban tells you more about how to manage the flow of work rather than how to release the work. However, there are few STEPS that might be helpful while RELEASING work or product in Kanban.

They are:

• Release in Kanban should be every two weeks on a schedule
• To avoid too many sticky notes in the “done” section, and to run the process smoothly, inform the BUSINESS unit about releasing the product or work
• Release the ITEM EARLY which is of high priority and needed immediately.

Kanban tells you more about how to manage the flow of work rather than how to release the work. However, there are few steps that might be helpful while releasing work or product in Kanban.

They are:

While USING KANBAN, the BEST way to TRACK progress is CUMULATIVE Flow Diagram. It replaces burndown/burnup chart for Kanban teams.

While using Kanban, the best way to track progress is Cumulative Flow Diagram. It replaces burndown/burnup chart for Kanban teams.

It is very important to DIFFERENTIATE the developers about the TEST case that is failed and returned and the test case that is ready or fresh to test. In ORDER to differentiate this to the developer, you can split READY option in KANBAN into two CATEGORIES a) Re-open b) Ready. Re-open option status will have test-cases that are failed while ready option should have new test case that is yet to be tested.

It is very important to differentiate the developers about the test case that is failed and returned and the test case that is ready or fresh to test. In order to differentiate this to the developer, you can split READY option in Kanban into two categories a) Re-open b) Ready. Re-open option status will have test-cases that are failed while ready option should have new test case that is yet to be tested.

To link card together in Kanban, there are two ways:

You can use TAGS to link two cards: FIRST you have to create cards and have to link cards using the same tag (Eg: guru99), and then you can search all TASKS linked using search option

Using unique URL: Each card in Kanban has unique URL, and you can copy this URL and paste it to ANOTHER card’s external link fields.

To link card together in Kanban, there are two ways:

You can use tags to link two cards: First you have to create cards and have to link cards using the same tag (Eg: guru99), and then you can search all tasks linked using search option

Using unique URL: Each card in Kanban has unique URL, and you can copy this URL and paste it to another card’s external link fields.

In Kanban, Power-ups ALLOWS you to customize your board as per your need.

 It adds various SPECTRUM of features to your Kanban board like:

• Card block
• Card aging
• Developer TOOLS
• Team activity widget
• Task navigator
• Auto-assign
• Add task box
• Calendar widget
• Web attachment

In Kanban, Power-ups allows you to customize your board as per your need.

 It adds various spectrum of features to your Kanban board like:

With the help of KANBAN, you can organize your work into projects:

• BUILD project teams
• Invite people to join the team
• Share and COLLABORATE on work to do- using online Kanban BOARDS.

With the help of Kanban, you can organize your work into projects:

In Kanban, with online document FEATURES you can do THINGS like:

• Pin up DOCUMENTS to tasks and upload them to your cloud storage
• Collaborate in REAL time on Google DRIVE
• Link to file on Box, Onedrive and Dropbox

In Kanban, with online document features you can do things like:

TIME tracker provides detail summary about the work done at that INSTANT of time.

It is useful in many WAYS like:

• Time reports by project, user or TASK
• Detailed reports about the work done
• MANAGEABLE time entries
• Easy time tracking

Time tracker provides detail summary about the work done at that instant of time.

It is useful in many ways like:

• Kanban analytics provides information about the workflow and removal of any bottlenecks
• Improves and monitor work efficiency
• Provides estimation time for the completion of the task
• To get a QUICK insight into project STATUS USE breakdown charts
• Using CUMULATIVE flow diagram measures cycle time

• It GIVES real-time visibility into what people are working on
• It helps you to visualize, optimize and take control of your workflow
• It helps to limit WORK in progress to prevent BOTTLENECKS
• It helps to COLLABORATE in real time with team members
• Using the horizontal swimlanes it helps to track multiple projects on ONE board.

Game developer OFTEN uses Heijunka board. The benefit of Heijunka board is that, UNLIKE SIMPLE scrum design board, this board ALLOWS all staff to work independently. This will reduce the redundancy among the team, and the team does not have to wait for another unit to FINISH their task.

Game developer often uses Heijunka board. The benefit of Heijunka board is that, unlike simple scrum design board, this board allows all staff to work independently. This will reduce the redundancy among the team, and the team does not have to wait for another unit to finish their task.

Kanban WORKS on THREE principles:

1. It helps to VISUALIZE the task you working on and the items in context of each other
2. It helps to balance the workflow for teams, so they don’t COMMIT themselves to unnecessary work or overburden of work
3. On completion of any work, it pulls out the most prioritized work from the backlog.

Kanban works on three principles:

Scrum:

• You have to do daily STANDUP meetings
• Iteration is a part of Scrum
• TASK is designed and structured in such a way that it fits within iteration
• Board is reset at every sprint
• The process INVOLVES three people scrum master, PRODUCT owner, and scrum team
• Retrospective is required

Kanban:

• Daily stand up meeting is not required
• Iteration can be used as optional; it can be even driven
• There is no size limit for the task
• Board is more or less remains same
• There are no defined ROLES
• Retrospective is not required

Scrum:

Kanban:

The advantage of using KANBAN is:

• It helps an organization to lower the costs
• It CREATES a work site that can respond to changes quickly
• It facilitates the methods of achieving and assuring quality control
• ALLOWS the team to reach their maximum POTENTIAL
• When priorities changes Kanban works best
• It can deliver feature faster due to their shorter cycle times
• Remove the activities that are of least concern or no concern to the team or organization
• Rapid feedback loops increase the CHANCES of more motivated, empowered and higher performing team members.

The advantage of using Kanban is:

A Kanban is a like a flash card carrying all the INFORMATION about the status of your WORK and the work required to be done on the product at each stage of software DEVELOPMENT cycle. In SIMPLE terms, it classifies your work in three categories, TO DO -> WORK IN PROGRESS -> DONE.

A Kanban is a like a flash card carrying all the information about the status of your work and the work required to be done on the product at each stage of software development cycle. In simple terms, it classifies your work in three categories, TO DO -> WORK IN PROGRESS -> DONE.