×
Can you Scale with Kanban? In-depth Review 

Can you Scale with Kanban? In-depth Review 

What works well for one team becomes chaos when scaled to a department or company level—especially if tools lack structure. Kanban can be great for small teams, but scaling it across a department or company gets messy. I’ve seen this happen. One product team thrived with their Kanban board—clear columns, flow, and daily check-ins. Then, when three other teams joined using the same board, chaos has bagan. Each team labeled tasks differently and lacked shared rules.  

Without a standardized process, no one knew who was doing what or why tasks were stuck. 

The issue worsens if the Kanban tool lacks features like swimlanes for team separation. For example, if your board shows one big “In Progress” column with tasks from five teams, it can get troublesome to find bottlenecks. 

Without reporting features, leadership can’t see how work is moving or if it’s stalled. What begins as a simple system for clarity can quickly turn into a confusing mess without the right structure. 

But it doesn’t have to be this way. I’ll share practical tips to structure your board, set clear rules, and pick the right tools to scale with Kanban. 

How Does Kanban Fit Into Scaling Agile Frameworks or Approaches?

In my experience, Kanban scales well because it’s flexible. I’ve seen teams use it alongside Scrum to visualize work-in-progress and surface bottlenecks without changing their sprint rituals.  

What makes Kanban powerful at scale is its adaptability. Whether you’re exploring Flight Levels, using Team Topologies, or blending methods, Kanban gives you a visual way to track and improve flow. 

Kanban Board Setup (Teamhood)

How Does Variability in Ticket Size Affect Kanban Forecasting?

Ticket sizes can vary a lot in Kanban, but that’s okay. Having smaller tasks that are around the same size does make forecasting a bit simpler, but you can still forecast with a mix of big and small tasks. If your work doesn’t seem to be averaging out and there’s a pattern, then it’s time to dig in.  

One way to handle variability is through a Service Level Expectation. For instance, you might say, “85% of our tasks are completed within 10 days,” based on past task durations.

How To Map Workflow in Kanban?

To map a workflow in Kanban, first understand how your team works. Then, make those steps clear.  

Think of the stages your work goes through, such as: Plan > Configure > Create test cases > Execute > Done. Each stage has rules to follow before moving on. 

Kanban Board Setup (Teamhood)

You can create different workflows based on the type of work. The board should display tasks and how the team agrees to handle them. This keeps everything clear and organized. 

How To Forecast Delivery or Plan in Kanban?

In Kanban, forecasting is based on past data and flow, using probabilities instead of exact averages. 

Tools like Monte Carlo Simulations help predict outcomes by showing chances, like “There’s an X% chance we’ll finish Y tasks in Z weeks.” This uses historical cycle times to give realistic delivery estimates. Unlike Scrum, Kanban doesn’t use velocity charts since it doesn’t work with fixed timeboxes like sprints. 

Forecasting this way helps keep stakeholders informed with more reliable timelines. 

Kanban vs. Scrum: Which Is Better for Scaling? 

There’s no clear winner between Kanban and Scrum for scaling because they can actually work together. Scrum uses fixed timeboxes called sprints. Kanban focuses on smooth flow and continuous delivery.

Kanban is ideal for tasks of varying sizes. It suits environments like support desks, where quick and ongoing task completion is essential.

Scrum works better when you need to plan deliveries for outside stakeholders with set deadlines, often using story points. If your team relies on story points and strict timeboxes, you’re probably leaning more toward Scrum. 

How Teamhood Solves Scalability 

I’ve found that Teamhood really makes it easier for you and your teams to work together without confusion. For example, if your team depends on another team’s work, Teamhood clearly shows these links. This way, nothing gets missed. With shared workspaces, everyone stays on the same page and sees the big picture. 

Teamhood helps you stay organized by linking tasks across boards and sharing resources. You can create custom roles and permissions to control who can see and do what.

This way, everything stays safe and clear. And whether you’re managing a few people or a whole department, Teamhood helps keep work moving forward. 

Closing Thoughts: Can You Scale with Kanban?

Closing Thoughts: Can You Scale with Kanban? Scaling Kanban isn’t simple, but it can work with the right approach. What suits a single team may become chaotic when expanded. This chaos arises without shared rules, clear workflows, and the right tools. It’s not a flaw in Kanban; it highlights the need for thoughtful system design. Kanban’s flexibility is its strength at scale.

Proper structure makes Kanban more than just a visual task board. It transforms it into a clear and scalable framework. You can align teams using Flight Levels, combine it with Scrum, or manage dependencies with tools like Teamhood.

So yes—you can scale with Kanban. Just don’t scale the chaos. Scale the clarity.

Source link
#Scale #Kanban #Indepth #Review


By providing a needed security patch to an older version of iOS last month, Apple tacitly—but unofficially—acknowledged that avoiding the Liquid Glass aesthetic is a valid choice.

Now, according to anonymous sources who spoke to Bloomberg’s Mark Gurman, an upcoming update will address problems with Liquid Glass in macOS 26. If you haven’t updated because you hate it, or are worried the design flaws make it unusable, you are seen.

Gurman writes that Apple “is preparing what people internally consider to be a ‘slight redesign’ for macOS 27,” and that the company is looking to fix, “shadows and transparency quirks.”

Gurman’s sources sound a bit defensive, however. They tell him the Liquid Glass update “didn’t necessarily suffer from design problems,” but instead had “a not-completely-baked implementation from Apple’s software engineering team.” The fixes, then, are supposed to “make Liquid Glass look the way Apple’s design team intended it to from the start.” Got it? The designers thought everything through from the beginning, but the artless neanderthals who built their designs into software—this thinking goes—let them down.

My first impression was that it was overly generous of Gurman to give voice to this framing of the Liquid Glass story, but I have to admit that it’s also a genuinely plausible explanation for just how hated the design scheme ended up being.

For instance, while Apple has already chipped away at some of the bigger problems, Tahoe shipped with some issues that were beyond annoying and actually interfered with usability, particularly for low vision people. Before the 26.3 update in February, as OS X Daily noted, choosing the option to reduce transparency “would leave considerable transparent effects, including in sidebars, headers, titlebars, search boxes, and more, leading to situations where text would overlap and interface elements would be washed out with blurry colors and interface elements.”

Then again, some designs were heavily criticized on an aesthetic basis, not as bad implementation. There’s probably no bigger Apple fan than John Gruber of Daring Fireball, and his take on the redesign of some of the icons was scorching: “I don’t think the old icons for these apps from MacOS 15 were particularly good — Apple has mostly lost its “icons look cool” game. But the new ones in MacOS 26 Tahoe are objectively terrible.”

Gurman has claimed in the past that Liquid Glass is sort of a long game, rolled out in advance of the release of the 20th anniversary iPhone, which he expects to be a huge design milestone for Apple. Supposedly, that phone’s overall vibe will benefit from Liquid Glass. When all is revealed, maybe the world will agree.

In the meantime, macOS is getting some tweaks, and we should expect, Gurman says, “more of a cleanup and refinement effort aligned with the company’s wider push to polish its software this year.”

#Apple #Reportedly #Retooling #Liquid #Glass #Problems #macOSApple,Liquid Glass,macos 27">Yes, Apple Is Reportedly Retooling Some Liquid Glass Problems for macOS 27
                By providing a needed security patch to an older version of iOS last month, Apple tacitly—but unofficially—acknowledged that avoiding the Liquid Glass aesthetic is a valid choice. Now, according to anonymous sources who spoke to Bloomberg’s Mark Gurman, an upcoming update will address problems with Liquid Glass in macOS 26. If you haven’t updated because you hate it, or are worried the design flaws make it unusable, you are seen.

 Gurman writes that Apple “is preparing what people internally consider to be a ‘slight redesign’ for macOS 27,” and that the company is looking to fix, “shadows and transparency quirks.” Gurman’s sources sound a bit defensive, however. They tell him the Liquid Glass update “didn’t necessarily suffer from design problems,” but instead had “a not-completely-baked implementation from Apple’s software engineering team.” The fixes, then, are supposed to “make Liquid Glass look the way Apple’s design team intended it to from the start.” Got it? The designers thought everything through from the beginning, but the artless neanderthals who built their designs into software—this thinking goes—let them down. My first impression was that it was overly generous of Gurman to give voice to this framing of the Liquid Glass story, but I have to admit that it’s also a genuinely plausible explanation for just how hated the design scheme ended up being. For instance, while Apple has already chipped away at some of the bigger problems, Tahoe shipped with some issues that were beyond annoying and actually interfered with usability, particularly for low vision people. Before the 26.3 update in February, as OS X Daily noted, choosing the option to reduce transparency “would leave considerable transparent effects, including in sidebars, headers, titlebars, search boxes, and more, leading to situations where text would overlap and interface elements would be washed out with blurry colors and interface elements.”

 Then again, some designs were heavily criticized on an aesthetic basis, not as bad implementation. There’s probably no bigger Apple fan than John Gruber of Daring Fireball, and his take on the redesign of some of the icons was scorching: “I don’t think the old icons for these apps from MacOS 15 were particularly good — Apple has mostly lost its “icons look cool” game. But the new ones in MacOS 26 Tahoe are objectively terrible.”

 Gurman has claimed in the past that Liquid Glass is sort of a long game, rolled out in advance of the release of the 20th anniversary iPhone, which he expects to be a huge design milestone for Apple. Supposedly, that phone’s overall vibe will benefit from Liquid Glass. When all is revealed, maybe the world will agree. In the meantime, macOS is getting some tweaks, and we should expect, Gurman says, “more of a cleanup and refinement effort aligned with the company’s wider push to polish its software this year.”      #Apple #Reportedly #Retooling #Liquid #Glass #Problems #macOSApple,Liquid Glass,macos 27

acknowledged that avoiding the Liquid Glass aesthetic is a valid choice.

Now, according to anonymous sources who spoke to Bloomberg’s Mark Gurman, an upcoming update will address problems with Liquid Glass in macOS 26. If you haven’t updated because you hate it, or are worried the design flaws make it unusable, you are seen.

Gurman writes that Apple “is preparing what people internally consider to be a ‘slight redesign’ for macOS 27,” and that the company is looking to fix, “shadows and transparency quirks.”

Gurman’s sources sound a bit defensive, however. They tell him the Liquid Glass update “didn’t necessarily suffer from design problems,” but instead had “a not-completely-baked implementation from Apple’s software engineering team.” The fixes, then, are supposed to “make Liquid Glass look the way Apple’s design team intended it to from the start.” Got it? The designers thought everything through from the beginning, but the artless neanderthals who built their designs into software—this thinking goes—let them down.

My first impression was that it was overly generous of Gurman to give voice to this framing of the Liquid Glass story, but I have to admit that it’s also a genuinely plausible explanation for just how hated the design scheme ended up being.

For instance, while Apple has already chipped away at some of the bigger problems, Tahoe shipped with some issues that were beyond annoying and actually interfered with usability, particularly for low vision people. Before the 26.3 update in February, as OS X Daily noted, choosing the option to reduce transparency “would leave considerable transparent effects, including in sidebars, headers, titlebars, search boxes, and more, leading to situations where text would overlap and interface elements would be washed out with blurry colors and interface elements.”

Then again, some designs were heavily criticized on an aesthetic basis, not as bad implementation. There’s probably no bigger Apple fan than John Gruber of Daring Fireball, and his take on the redesign of some of the icons was scorching: “I don’t think the old icons for these apps from MacOS 15 were particularly good — Apple has mostly lost its “icons look cool” game. But the new ones in MacOS 26 Tahoe are objectively terrible.”

Gurman has claimed in the past that Liquid Glass is sort of a long game, rolled out in advance of the release of the 20th anniversary iPhone, which he expects to be a huge design milestone for Apple. Supposedly, that phone’s overall vibe will benefit from Liquid Glass. When all is revealed, maybe the world will agree.

In the meantime, macOS is getting some tweaks, and we should expect, Gurman says, “more of a cleanup and refinement effort aligned with the company’s wider push to polish its software this year.”

#Apple #Reportedly #Retooling #Liquid #Glass #Problems #macOSApple,Liquid Glass,macos 27">Yes, Apple Is Reportedly Retooling Some Liquid Glass Problems for macOS 27Yes, Apple Is Reportedly Retooling Some Liquid Glass Problems for macOS 27
                By providing a needed security patch to an older version of iOS last month, Apple tacitly—but unofficially—acknowledged that avoiding the Liquid Glass aesthetic is a valid choice. Now, according to anonymous sources who spoke to Bloomberg’s Mark Gurman, an upcoming update will address problems with Liquid Glass in macOS 26. If you haven’t updated because you hate it, or are worried the design flaws make it unusable, you are seen.

 Gurman writes that Apple “is preparing what people internally consider to be a ‘slight redesign’ for macOS 27,” and that the company is looking to fix, “shadows and transparency quirks.” Gurman’s sources sound a bit defensive, however. They tell him the Liquid Glass update “didn’t necessarily suffer from design problems,” but instead had “a not-completely-baked implementation from Apple’s software engineering team.” The fixes, then, are supposed to “make Liquid Glass look the way Apple’s design team intended it to from the start.” Got it? The designers thought everything through from the beginning, but the artless neanderthals who built their designs into software—this thinking goes—let them down. My first impression was that it was overly generous of Gurman to give voice to this framing of the Liquid Glass story, but I have to admit that it’s also a genuinely plausible explanation for just how hated the design scheme ended up being. For instance, while Apple has already chipped away at some of the bigger problems, Tahoe shipped with some issues that were beyond annoying and actually interfered with usability, particularly for low vision people. Before the 26.3 update in February, as OS X Daily noted, choosing the option to reduce transparency “would leave considerable transparent effects, including in sidebars, headers, titlebars, search boxes, and more, leading to situations where text would overlap and interface elements would be washed out with blurry colors and interface elements.”

 Then again, some designs were heavily criticized on an aesthetic basis, not as bad implementation. There’s probably no bigger Apple fan than John Gruber of Daring Fireball, and his take on the redesign of some of the icons was scorching: “I don’t think the old icons for these apps from MacOS 15 were particularly good — Apple has mostly lost its “icons look cool” game. But the new ones in MacOS 26 Tahoe are objectively terrible.”

 Gurman has claimed in the past that Liquid Glass is sort of a long game, rolled out in advance of the release of the 20th anniversary iPhone, which he expects to be a huge design milestone for Apple. Supposedly, that phone’s overall vibe will benefit from Liquid Glass. When all is revealed, maybe the world will agree. In the meantime, macOS is getting some tweaks, and we should expect, Gurman says, “more of a cleanup and refinement effort aligned with the company’s wider push to polish its software this year.”      #Apple #Reportedly #Retooling #Liquid #Glass #Problems #macOSApple,Liquid Glass,macos 27

By providing a needed security patch to an older version of iOS last month, Apple tacitly—but unofficially—acknowledged that avoiding the Liquid Glass aesthetic is a valid choice.

Now, according to anonymous sources who spoke to Bloomberg’s Mark Gurman, an upcoming update will address problems with Liquid Glass in macOS 26. If you haven’t updated because you hate it, or are worried the design flaws make it unusable, you are seen.

Gurman writes that Apple “is preparing what people internally consider to be a ‘slight redesign’ for macOS 27,” and that the company is looking to fix, “shadows and transparency quirks.”

Gurman’s sources sound a bit defensive, however. They tell him the Liquid Glass update “didn’t necessarily suffer from design problems,” but instead had “a not-completely-baked implementation from Apple’s software engineering team.” The fixes, then, are supposed to “make Liquid Glass look the way Apple’s design team intended it to from the start.” Got it? The designers thought everything through from the beginning, but the artless neanderthals who built their designs into software—this thinking goes—let them down.

My first impression was that it was overly generous of Gurman to give voice to this framing of the Liquid Glass story, but I have to admit that it’s also a genuinely plausible explanation for just how hated the design scheme ended up being.

For instance, while Apple has already chipped away at some of the bigger problems, Tahoe shipped with some issues that were beyond annoying and actually interfered with usability, particularly for low vision people. Before the 26.3 update in February, as OS X Daily noted, choosing the option to reduce transparency “would leave considerable transparent effects, including in sidebars, headers, titlebars, search boxes, and more, leading to situations where text would overlap and interface elements would be washed out with blurry colors and interface elements.”

Then again, some designs were heavily criticized on an aesthetic basis, not as bad implementation. There’s probably no bigger Apple fan than John Gruber of Daring Fireball, and his take on the redesign of some of the icons was scorching: “I don’t think the old icons for these apps from MacOS 15 were particularly good — Apple has mostly lost its “icons look cool” game. But the new ones in MacOS 26 Tahoe are objectively terrible.”

Gurman has claimed in the past that Liquid Glass is sort of a long game, rolled out in advance of the release of the 20th anniversary iPhone, which he expects to be a huge design milestone for Apple. Supposedly, that phone’s overall vibe will benefit from Liquid Glass. When all is revealed, maybe the world will agree.

In the meantime, macOS is getting some tweaks, and we should expect, Gurman says, “more of a cleanup and refinement effort aligned with the company’s wider push to polish its software this year.”

#Apple #Reportedly #Retooling #Liquid #Glass #Problems #macOSApple,Liquid Glass,macos 27

After three people died on a cruise ship struck by a hantavirus, authorities are actively tracking down 29 people who had left the ship. They’re trying to trace the spread of the virus. It’s a long, arduous, global process to find and notify people who might be at risk of infection.

Hey, wasn’t there supposed to be an app for that?

Contact-tracing apps were a global effort starting in 2020 during the Covid-19 pandemic. Enabled by phone companies like Apple and Google, contact tracing was designed to use Bluetooth connections to detect when people had come in contact with someone who had or would later test positive for Covid and report as much. It didn’t do much to solve the spread of the pandemic, but tracking the virus became more effective at least. The same process wouldn’t go well for the hantavirus problem.

“There is no use of apps for this hantavirus outbreak,” Emily Gurley, an epidemiologist at Johns Hopkins University, wrote in an email response to WIRED. “The number of cases are small, and it’s important to trace all contacts exactly to stop transmission.”

On a smaller scale of infection like this, officials have to start at the source (an infected individual), then go person-by-person, confirming where they went and who they might have come into contact with. Data collected by apps from a broad swath of devices would not be anywhere close to accurate enough to give a good idea of where the virus might have hitchhiked to next.

Contact tracing on a wider scale, like, say, a global pandemic, is less about tracking the individual infections and more about understanding what parts of the population might be affected, giving people the opportunity to self-quarantine after exposure. But that depends on how people choose to respond, and how the technology is utilized by public emergency systems. During the Covid pandemic, contact-tracing via apps tended to work better in more carefully managed European countries, but did not slow the spread in the US.

Making devices accessible to that kind of proximity information has also brought all sorts of concerns about privacy, given that the technology would require always-on access to work properly. Contact tracing also struggled to maintain accuracy, and in some cases could be providing false negatives or positives that don’t help further real information about the spread of the virus.

Especially in the case of something like the Hantavirus, where every person on that cruise ship can theoretically be directly tracked and contacted, it’s better to do that process the hard way.

“During small but highly fatal outbreaks, more precision is required,” Gurley wrote.

#ContactTracing #Apps #Hantaviruscoronavirus,covid-19,viruses,health,pandemics">Could Contact-Tracing Apps Help With the Hantavirus? Not ReallyAfter three people died on a cruise ship struck by a hantavirus, authorities are actively tracking down 29 people who had left the ship. They’re trying to trace the spread of the virus. It’s a long, arduous, global process to find and notify people who might be at risk of infection.Hey, wasn’t there supposed to be an app for that?Contact-tracing apps were a global effort starting in 2020 during the Covid-19 pandemic. Enabled by phone companies like Apple and Google, contact tracing was designed to use Bluetooth connections to detect when people had come in contact with someone who had or would later test positive for Covid and report as much. It didn’t do much to solve the spread of the pandemic, but tracking the virus became more effective at least. The same process wouldn’t go well for the hantavirus problem.“There is no use of apps for this hantavirus outbreak,” Emily Gurley, an epidemiologist at Johns Hopkins University, wrote in an email response to WIRED. “The number of cases are small, and it’s important to trace all contacts exactly to stop transmission.”On a smaller scale of infection like this, officials have to start at the source (an infected individual), then go person-by-person, confirming where they went and who they might have come into contact with. Data collected by apps from a broad swath of devices would not be anywhere close to accurate enough to give a good idea of where the virus might have hitchhiked to next.Contact tracing on a wider scale, like, say, a global pandemic, is less about tracking the individual infections and more about understanding what parts of the population might be affected, giving people the opportunity to self-quarantine after exposure. But that depends on how people choose to respond, and how the technology is utilized by public emergency systems. During the Covid pandemic, contact-tracing via apps tended to work better in more carefully managed European countries, but did not slow the spread in the US.Making devices accessible to that kind of proximity information has also brought all sorts of concerns about privacy, given that the technology would require always-on access to work properly. Contact tracing also struggled to maintain accuracy, and in some cases could be providing false negatives or positives that don’t help further real information about the spread of the virus.Especially in the case of something like the Hantavirus, where every person on that cruise ship can theoretically be directly tracked and contacted, it’s better to do that process the hard way.“During small but highly fatal outbreaks, more precision is required,” Gurley wrote.#ContactTracing #Apps #Hantaviruscoronavirus,covid-19,viruses,health,pandemics

hantavirus, authorities are actively tracking down 29 people who had left the ship. They’re trying to trace the spread of the virus. It’s a long, arduous, global process to find and notify people who might be at risk of infection.

Hey, wasn’t there supposed to be an app for that?

Contact-tracing apps were a global effort starting in 2020 during the Covid-19 pandemic. Enabled by phone companies like Apple and Google, contact tracing was designed to use Bluetooth connections to detect when people had come in contact with someone who had or would later test positive for Covid and report as much. It didn’t do much to solve the spread of the pandemic, but tracking the virus became more effective at least. The same process wouldn’t go well for the hantavirus problem.

“There is no use of apps for this hantavirus outbreak,” Emily Gurley, an epidemiologist at Johns Hopkins University, wrote in an email response to WIRED. “The number of cases are small, and it’s important to trace all contacts exactly to stop transmission.”

On a smaller scale of infection like this, officials have to start at the source (an infected individual), then go person-by-person, confirming where they went and who they might have come into contact with. Data collected by apps from a broad swath of devices would not be anywhere close to accurate enough to give a good idea of where the virus might have hitchhiked to next.

Contact tracing on a wider scale, like, say, a global pandemic, is less about tracking the individual infections and more about understanding what parts of the population might be affected, giving people the opportunity to self-quarantine after exposure. But that depends on how people choose to respond, and how the technology is utilized by public emergency systems. During the Covid pandemic, contact-tracing via apps tended to work better in more carefully managed European countries, but did not slow the spread in the US.

Making devices accessible to that kind of proximity information has also brought all sorts of concerns about privacy, given that the technology would require always-on access to work properly. Contact tracing also struggled to maintain accuracy, and in some cases could be providing false negatives or positives that don’t help further real information about the spread of the virus.

Especially in the case of something like the Hantavirus, where every person on that cruise ship can theoretically be directly tracked and contacted, it’s better to do that process the hard way.

“During small but highly fatal outbreaks, more precision is required,” Gurley wrote.

#ContactTracing #Apps #Hantaviruscoronavirus,covid-19,viruses,health,pandemics">Could Contact-Tracing Apps Help With the Hantavirus? Not Really

After three people died on a cruise ship struck by a hantavirus, authorities are actively tracking down 29 people who had left the ship. They’re trying to trace the spread of the virus. It’s a long, arduous, global process to find and notify people who might be at risk of infection.

Hey, wasn’t there supposed to be an app for that?

Contact-tracing apps were a global effort starting in 2020 during the Covid-19 pandemic. Enabled by phone companies like Apple and Google, contact tracing was designed to use Bluetooth connections to detect when people had come in contact with someone who had or would later test positive for Covid and report as much. It didn’t do much to solve the spread of the pandemic, but tracking the virus became more effective at least. The same process wouldn’t go well for the hantavirus problem.

“There is no use of apps for this hantavirus outbreak,” Emily Gurley, an epidemiologist at Johns Hopkins University, wrote in an email response to WIRED. “The number of cases are small, and it’s important to trace all contacts exactly to stop transmission.”

On a smaller scale of infection like this, officials have to start at the source (an infected individual), then go person-by-person, confirming where they went and who they might have come into contact with. Data collected by apps from a broad swath of devices would not be anywhere close to accurate enough to give a good idea of where the virus might have hitchhiked to next.

Contact tracing on a wider scale, like, say, a global pandemic, is less about tracking the individual infections and more about understanding what parts of the population might be affected, giving people the opportunity to self-quarantine after exposure. But that depends on how people choose to respond, and how the technology is utilized by public emergency systems. During the Covid pandemic, contact-tracing via apps tended to work better in more carefully managed European countries, but did not slow the spread in the US.

Making devices accessible to that kind of proximity information has also brought all sorts of concerns about privacy, given that the technology would require always-on access to work properly. Contact tracing also struggled to maintain accuracy, and in some cases could be providing false negatives or positives that don’t help further real information about the spread of the virus.

Especially in the case of something like the Hantavirus, where every person on that cruise ship can theoretically be directly tracked and contacted, it’s better to do that process the hard way.

“During small but highly fatal outbreaks, more precision is required,” Gurley wrote.

#ContactTracing #Apps #Hantaviruscoronavirus,covid-19,viruses,health,pandemics

Post Comment