Empower your R&D with automated analytics
Get data-driven insights to deliver projects on time
Screenful helps engineering leaders to optimize their software delivery so they can build the right things faster. Gain visibility across your engineering organization to improve predictability, reduce costs, and increase customer satisfaction.
Features
Data to drive decisions at every level
Capture engineering KPIs
Get the engineering metrics you need - the lead and cycle times, team velocity, work-in-progress, and more. Get data-driven forecasts based on your historical velocity. Instead of guesswork, you can use the data to make your own judgment!
Capture engineering KPIs
Get the engineering metrics you need - the lead and cycle times, team velocity, work-in-progress, and more. Get data-driven forecasts based on your historical velocity. Instead of guesswork, you can use the data to make your own judgment!
Consolidate Your Data into Actionable Insights
Stop constantly switching between platforms. Screenful centralizes all engineering data for complete analysis and reporting.
Consolidate Your Data into Actionable Insights
Stop constantly switching between platforms. Screenful centralizes all engineering data for complete analysis and reporting.
Easily Share Metrics Across the Organization
Distribute reports to showcase engineering progress and blockers with stakeholders. Real-time visibility builds trusted relationships.
Easily Share Metrics Across the Organization
Distribute reports to showcase engineering progress and blockers with stakeholders. Real-time visibility builds trusted relationships.
Keep Engineering Teams Informed
Share reports to keep teams updated on productivity goals and performance. Add context to guide teams and align everyone.
Keep Engineering Teams Informed
Share reports to keep teams updated on productivity goals and performance. Add context to guide teams and align everyone.
Schedule and Share Reports with Ease
Deliver monthly, weekly or even daily updates without any extra effort. Screenful lets you schedule report distribution on any cadence directly to stakeholders. Say goodbye to scrambling to pull presentations together. Automated reporting makes it easy to share progress consistently.
Schedule and Share Reports with Ease
Deliver monthly, weekly or even daily updates without any extra effort. Screenful lets you schedule report distribution on any cadence directly to stakeholders. Say goodbye to scrambling to pull presentations together. Automated reporting makes it easy to share progress consistently.
Integrations
Works with tools you already use
Loved by industry leaders
Screenful was best in every category. It beautifully and simply highlights key agile metrics for our whole in-office team and any visiting stakeholders.
Jesse Fewell
Agile coach, writer, trainer
I love Screenful for its user-friendly interface and seamless integration to multiple data sources. The customer service is outstanding; they provided exceptional support whenever we needed it!
Tasnia Rehnuma Mahmud
Project Coordinator at Fashion Snoops
Outright best reporting tool. We have tried many different ones over the past 2 years, and none of them beats Screenful. The ability to build custom reports provides amazing capabilities for agile teams.
Akaki Meladze
Director of Engineering at Singular
Using visual boards without metrics misses the whole point of improving performance. Screenful is a must have tool for our Kanban.
Jaxon Klein
CEO & Co-founder at Keyo Inc.
We've been using Screenful for 13 months now and we can't say enough good things about it. The insight we have is invaluable to us and has helped us keep the delivery capacity at a steady temperature.
Fabien Arcellier
CTO & Co-founder at Stackeo
Screenful is a wonderful visualization tool that I use to illustrate to organizations why they should relentlessly focus on reducing lead time & cycle time, understand cumulative flow and decompose work.
Patrick Ingram
Enterprise Agility Consultant
Accenture is working with Screenful to roll out best practice agile metrics in minutes - allowing our world class delivery teams to be led by data.
Kit Friend
Business & Technology Innovation Senior Principle, Accenture UK
Screenful allows me to easily identify where I am spending time so that I can ensure I'm working on the right things. The weekly email is a great summary delivered right to my phone
Andy Wheeldon
Agile coach
Screenful was best in every category. It beautifully and simply highlights key agile metrics for our whole in-office team and any visiting stakeholders.
Jesse Fewell
Agile coach, writer, trainer
I love Screenful for its user-friendly interface and seamless integration to multiple data sources. The customer service is outstanding; they provided exceptional support whenever we needed it!
Tasnia Rehnuma Mahmud
Project Coordinator at Fashion Snoops
Outright best reporting tool. We have tried many different ones over the past 2 years, and none of them beats Screenful. The ability to build custom reports provides amazing capabilities for agile teams.
Akaki Meladze
Director of Engineering at Singular
Using visual boards without metrics misses the whole point of improving performance. Screenful is a must have tool for our Kanban.
Jaxon Klein
CEO & Co-founder at Keyo Inc.
We've been using Screenful for 13 months now and we can't say enough good things about it. The insight we have is invaluable to us and has helped us keep the delivery capacity at a steady temperature.
Fabien Arcellier
CTO & Co-founder at Stackeo
Screenful is a wonderful visualization tool that I use to illustrate to organizations why they should relentlessly focus on reducing lead time & cycle time, understand cumulative flow and decompose work.
Patrick Ingram
Enterprise Agility Consultant
Accenture is working with Screenful to roll out best practice agile metrics in minutes - allowing our world class delivery teams to be led by data.
Kit Friend
Business & Technology Innovation Senior Principle, Accenture UK
Screenful allows me to easily identify where I am spending time so that I can ensure I'm working on the right things. The weekly email is a great summary delivered right to my phone
Andy Wheeldon
Agile coach
trusted by the world’s most innovative businesses
trusted by the world’s most innovative businesses
trusted by the world’s most innovative businesses
Automated project reporting made easy for everyone
The award-winning data visualization tool that fits the needs of all stakeholders
How could we deliver more while keeping the quality high?
What are the highest priority tasks I should be focusing on next?
What is the status of our project – will it be delivered on time?
Team Lead
Business
Developer
Sales
Client
Which sales channels are driving the most revenue for us?
Are there any trends in our deals pipeline that I should be aware of?
Automated project reporting made easy for everyone
The award-winning data visualization tool that fits the needs of all stakeholders
How could we deliver more while keeping the quality high?
What are the highest priority tasks I should be focusing on next?
What is the status of our project – will it be delivered on time?
Team Lead
Business
Developer
Sales
Client
Which sales channels are driving the most revenue for us?
Are there any trends in our deals pipeline that I should be aware of?
"Really good looking views and easy setup. Ideal for providing open visibility for the progress across the company."
complete toolkit
Zero to value in minutes
Streamline your reporting process with Screenful. Say goodbye to manual busywork so you can focus on delivering value.
FAQ
Common questions
The workflow settings specify when the work is started on a task and when it's completed. It is used to calculate metrics such as work in progress and velocity, as well as to measure the lead and cycle time of tasks. The tasks in the workflow states mapped to excluded won't be imported to Screenful.
You can learn more about workflow settings from the guides below:
The workflow settings specify when the work is started on a task and when it's completed. It is used to calculate metrics such as work in progress and velocity, as well as to measure the lead and cycle time of tasks. The tasks in the workflow states mapped to excluded won't be imported to Screenful.
You can learn more about workflow settings from the guides below:
We do not make changes to your data. We only read it via the API of your tool. Screenful is only for reporting and analytics. It does not update any data within your tools.
We do not make changes to your data. We only read it via the API of your tool. Screenful is only for reporting and analytics. It does not update any data within your tools.
What is the difference between these metrics?
Reaction time = time before the work was started
Cycle time = time from start to completion
Lead time = Reaction time + Cycle time
How is the reaction time calculated?
Reaction time starts running when a task is moved into a state that is mapped to the "Not started" in the workflow mapping. The reaction time stops when the task is moved out from that state. If the task is never placed into a state that is mapped to the “Not started” workflow state, then the reaction time is zero.
What if tasks skip lists/columns, or there is no sequential workflow?
The timing information is based on how long items stay in the workflow states that are mapped to "In progress" in the workflow mapping. There is no need for sequential progress, and it is totally fine if tasks skip some of the workflow steps.
What if a task is moved from the “not started” state directly to “done” without going through any of the “in progress” states?
In that case, the cycle time will be zero.
How does the cycle time work if a task is moved into "in progress" and then back to "not started yet"? Similarly, what happens if a card is archived while it's in progress?
Cycle time is calculated only for completed tasks, so in both of those cases, cycle time would be undefined.
If a task is moved from "in progress" to "done", but then back to "in progress" again for additional work would this time be added to the cycle time?
Cycle time is counted only when the task is in progress, so the time spent in the "done" state is not included in the calculation.
When is a task created? Does the clock start when a task is created or when it is put in the "next" state (or equivalent)?
The clock starts when a task is moved to a workflow state that is mapped to the "not started" or "in progress" workflow state.
Are weekends included in the cycle time calculations?
Weekends are included in the calculations by default, but you can change that in the chart settings by selecting 'Exclude non-business hours. See How to set weekend days and office hours
What is the difference between these metrics?
Reaction time = time before the work was started
Cycle time = time from start to completion
Lead time = Reaction time + Cycle time
How is the reaction time calculated?
Reaction time starts running when a task is moved into a state that is mapped to the "Not started" in the workflow mapping. The reaction time stops when the task is moved out from that state. If the task is never placed into a state that is mapped to the “Not started” workflow state, then the reaction time is zero.
What if tasks skip lists/columns, or there is no sequential workflow?
The timing information is based on how long items stay in the workflow states that are mapped to "In progress" in the workflow mapping. There is no need for sequential progress, and it is totally fine if tasks skip some of the workflow steps.
What if a task is moved from the “not started” state directly to “done” without going through any of the “in progress” states?
In that case, the cycle time will be zero.
How does the cycle time work if a task is moved into "in progress" and then back to "not started yet"? Similarly, what happens if a card is archived while it's in progress?
Cycle time is calculated only for completed tasks, so in both of those cases, cycle time would be undefined.
If a task is moved from "in progress" to "done", but then back to "in progress" again for additional work would this time be added to the cycle time?
Cycle time is counted only when the task is in progress, so the time spent in the "done" state is not included in the calculation.
When is a task created? Does the clock start when a task is created or when it is put in the "next" state (or equivalent)?
The clock starts when a task is moved to a workflow state that is mapped to the "not started" or "in progress" workflow state.
Are weekends included in the cycle time calculations?
Weekends are included in the calculations by default, but you can change that in the chart settings by selecting 'Exclude non-business hours. See How to set weekend days and office hours
By default yes, but you can specify your working hours and days in the Account Settings.
By default yes, but you can specify your working hours and days in the Account Settings.
If you want to exclude individual items from the metrics, you can do it by following the steps below
Set a specific label or tag (e.g. "excluded") to the item you want to exclude (task, issue, user story etc.)
Go to Screenful and reset the data source in the Data sync options
Go to the chart in question and set a filter (e.g. label is none of 'excluded')
If the item is already archived, you have to unarchive it first. Then apply the steps 1-2. After that, you can archive it again.
If you want to exclude individual items from the metrics, you can do it by following the steps below
Set a specific label or tag (e.g. "excluded") to the item you want to exclude (task, issue, user story etc.)
Go to Screenful and reset the data source in the Data sync options
Go to the chart in question and set a filter (e.g. label is none of 'excluded')
If the item is already archived, you have to unarchive it first. Then apply the steps 1-2. After that, you can archive it again.
Does this support my specific workflow or do I have to use some specific states like "open", "in progress" and "done"?
You are not limited to any specific set of states or a workflow. You can configure your own workflow, if such exists, and you can use that in your reporting. It's also ok if you don't have any workflow in your boards, as can create reports based on any other criteria by setting a filter.
You are not limited to any specific set of states or a workflow. You can configure your own workflow, if such exists, and you can use that in your reporting. It's also ok if you don't have any workflow in your boards, as can create reports based on any other criteria by setting a filter.
All data sources are synced automatically once per hour. Changing settings or configuration will trigger additional sync so your data is at most one hour old. You can sync data manually at any time in the sync settings.
All data sources are synced automatically once per hour. Changing settings or configuration will trigger additional sync so your data is at most one hour old. You can sync data manually at any time in the sync settings.
You can embed any custom chart or report to any web page using the embed code. Learn more about the sharing feature from the online guide.
You can embed any custom chart or report to any web page using the embed code. Learn more about the sharing feature from the online guide.
The Getting Started Guide contains Instructions for setting up Screenful.
See also our Accounts & Pricing FAQ.
Check out our how-to and video tutorials, or get in touch by emailing support@screenful.com
The Getting Started Guide contains Instructions for setting up Screenful.
See also our Accounts & Pricing FAQ.
Check out our how-to and video tutorials, or get in touch by emailing support@screenful.com
FAQ
Common questions
The workflow settings specify when the work is started on a task and when it's completed. It is used to calculate metrics such as work in progress and velocity, as well as to measure the lead and cycle time of tasks. The tasks in the workflow states mapped to excluded won't be imported to Screenful.
You can learn more about workflow settings from the guides below:
The workflow settings specify when the work is started on a task and when it's completed. It is used to calculate metrics such as work in progress and velocity, as well as to measure the lead and cycle time of tasks. The tasks in the workflow states mapped to excluded won't be imported to Screenful.
You can learn more about workflow settings from the guides below:
We do not make changes to your data. We only read it via the API of your tool. Screenful is only for reporting and analytics. It does not update any data within your tools.
We do not make changes to your data. We only read it via the API of your tool. Screenful is only for reporting and analytics. It does not update any data within your tools.
What is the difference between these metrics?
Reaction time = time before the work was started
Cycle time = time from start to completion
Lead time = Reaction time + Cycle time
How is the reaction time calculated?
Reaction time starts running when a task is moved into a state that is mapped to the "Not started" in the workflow mapping. The reaction time stops when the task is moved out from that state. If the task is never placed into a state that is mapped to the “Not started” workflow state, then the reaction time is zero.
What if tasks skip lists/columns, or there is no sequential workflow?
The timing information is based on how long items stay in the workflow states that are mapped to "In progress" in the workflow mapping. There is no need for sequential progress, and it is totally fine if tasks skip some of the workflow steps.
What if a task is moved from the “not started” state directly to “done” without going through any of the “in progress” states?
In that case, the cycle time will be zero.
How does the cycle time work if a task is moved into "in progress" and then back to "not started yet"? Similarly, what happens if a card is archived while it's in progress?
Cycle time is calculated only for completed tasks, so in both of those cases, cycle time would be undefined.
If a task is moved from "in progress" to "done", but then back to "in progress" again for additional work would this time be added to the cycle time?
Cycle time is counted only when the task is in progress, so the time spent in the "done" state is not included in the calculation.
When is a task created? Does the clock start when a task is created or when it is put in the "next" state (or equivalent)?
The clock starts when a task is moved to a workflow state that is mapped to the "not started" or "in progress" workflow state.
Are weekends included in the cycle time calculations?
Weekends are included in the calculations by default, but you can change that in the chart settings by selecting 'Exclude non-business hours. See How to set weekend days and office hours
What is the difference between these metrics?
Reaction time = time before the work was started
Cycle time = time from start to completion
Lead time = Reaction time + Cycle time
How is the reaction time calculated?
Reaction time starts running when a task is moved into a state that is mapped to the "Not started" in the workflow mapping. The reaction time stops when the task is moved out from that state. If the task is never placed into a state that is mapped to the “Not started” workflow state, then the reaction time is zero.
What if tasks skip lists/columns, or there is no sequential workflow?
The timing information is based on how long items stay in the workflow states that are mapped to "In progress" in the workflow mapping. There is no need for sequential progress, and it is totally fine if tasks skip some of the workflow steps.
What if a task is moved from the “not started” state directly to “done” without going through any of the “in progress” states?
In that case, the cycle time will be zero.
How does the cycle time work if a task is moved into "in progress" and then back to "not started yet"? Similarly, what happens if a card is archived while it's in progress?
Cycle time is calculated only for completed tasks, so in both of those cases, cycle time would be undefined.
If a task is moved from "in progress" to "done", but then back to "in progress" again for additional work would this time be added to the cycle time?
Cycle time is counted only when the task is in progress, so the time spent in the "done" state is not included in the calculation.
When is a task created? Does the clock start when a task is created or when it is put in the "next" state (or equivalent)?
The clock starts when a task is moved to a workflow state that is mapped to the "not started" or "in progress" workflow state.
Are weekends included in the cycle time calculations?
Weekends are included in the calculations by default, but you can change that in the chart settings by selecting 'Exclude non-business hours. See How to set weekend days and office hours
By default yes, but you can specify your working hours and days in the Account Settings.
By default yes, but you can specify your working hours and days in the Account Settings.
If you want to exclude individual items from the metrics, you can do it by following the steps below
Set a specific label or tag (e.g. "excluded") to the item you want to exclude (task, issue, user story etc.)
Go to Screenful and reset the data source in the Data sync options
Go to the chart in question and set a filter (e.g. label is none of 'excluded')
If the item is already archived, you have to unarchive it first. Then apply the steps 1-2. After that, you can archive it again.
If you want to exclude individual items from the metrics, you can do it by following the steps below
Set a specific label or tag (e.g. "excluded") to the item you want to exclude (task, issue, user story etc.)
Go to Screenful and reset the data source in the Data sync options
Go to the chart in question and set a filter (e.g. label is none of 'excluded')
If the item is already archived, you have to unarchive it first. Then apply the steps 1-2. After that, you can archive it again.
Does this support my specific workflow or do I have to use some specific states like "open", "in progress" and "done"?
You are not limited to any specific set of states or a workflow. You can configure your own workflow, if such exists, and you can use that in your reporting. It's also ok if you don't have any workflow in your boards, as can create reports based on any other criteria by setting a filter.
You are not limited to any specific set of states or a workflow. You can configure your own workflow, if such exists, and you can use that in your reporting. It's also ok if you don't have any workflow in your boards, as can create reports based on any other criteria by setting a filter.
All data sources are synced automatically once per hour. Changing settings or configuration will trigger additional sync so your data is at most one hour old. You can sync data manually at any time in the sync settings.
All data sources are synced automatically once per hour. Changing settings or configuration will trigger additional sync so your data is at most one hour old. You can sync data manually at any time in the sync settings.
You can embed any custom chart or report to any web page using the embed code. Learn more about the sharing feature from the online guide.
You can embed any custom chart or report to any web page using the embed code. Learn more about the sharing feature from the online guide.
The Getting Started Guide contains Instructions for setting up Screenful.
See also our Accounts & Pricing FAQ.
Check out our how-to and video tutorials, or get in touch by emailing support@screenful.com
The Getting Started Guide contains Instructions for setting up Screenful.
See also our Accounts & Pricing FAQ.
Check out our how-to and video tutorials, or get in touch by emailing support@screenful.com