How do I manage a Quantum Computing research project using Agile Scrum?
I’m a Project Manager assigned to a R&D team building a neutral-atom quantum computer. My developers complain that "Research isn't a User Story" and that two-week sprints are too short for physics experiments. How do I adapt Agile to a domain where a "successful" sprint might just be proving that a laser alignment failed for a reason we don't yet understand?
2025-03-25 in Project Management by Kevin Foster
| 12415 Views
All answers to this question.
In Quantum R&D, you should move from "Product Sprints" to "Learning Sprints." Instead of a functional feature, the "Definition of Done" for a story should be "Validated Learning." For example, a story isn't "Align the laser," it's "Document the interference pattern with 95% confidence." Use "Spikes" extensively—time-boxed research tasks that allow for failure. This maintains the rhythm of the Scrum ceremonies without forcing the physicists to fake progress. I also recommend a "Kanban-Scrum Hybrid" (Scrumban). This allows for the high-level roadmap of Scrum but the "pull-based" flow of Kanban, which better handles the unpredictable nature of experimental physics.
Answered 2025-03-27 by Dorothy Young
Do you find that a "Monthly Milestone" approach works better than bi-weekly sprints for hardware-heavy projects where parts have long lead times?
Answered 2025-03-29 by Kenneth Hill
-
Kenneth, that’s exactly the "Waterfall-Agile" hybrid we often settle on. Hardware procurement and major lab builds follow a Waterfall path because of the physical constraints (you can't "Agile" a custom vacuum chamber delivery). However, the software and control logic layers must remain Agile. By syncing the hardware milestones with the software sprints, you ensure that as soon as the chamber arrives, the code is ready to test. It’s about managing the "Interface" between the certain (hardware) and the uncertain (quantum software), which is the core challenge of any PM in the deep tech space.
Commented 2025-03-30 by Brian Scott
Don't forget the "Retrospective." In research, the retro is the most important meeting to figure out why a hypothesis failed and pivot the next sprint immediately.
Answered 2025-03-31 by Nancy Adams
-
Nancy is spot on. A "failed" experiment is only a failure if you don't learn from it. The Retro turns those failures into the roadmap for the next breakthrough.
Commented 2025-04-01 by Kevin Foster
Write a Comment
Your email address will not be published. Required fields are marked (*)

