If you’re thinking about applying agile methods to physical products, you may be struggling with how to build your backlog. For software, it’s straightforward since the user stories you created to kick off your project can be directly entered into the backlog and prioritized. A software scrum team will then pull the highest priority user stories and get started. But as we’ve discussed in previous articles, hardware backlogs are more complex. User stories often don’t directly translate to tasks and the diversity of work will include everything from conceptual design to detailed electrical engineering tasks. To learn more about this challenge, join JavaBrew on their Modified Agile for Hardware Development journey as we walk through nine steps starting with their initial project plan all the way through to their completed advanced coffee maker.
𝗪𝗵𝘆 𝗛𝗮𝗿𝗱𝘄𝗮𝗿𝗲 𝗔𝗴𝗶𝗹𝗲 𝗕𝗮𝗰𝗸𝗹𝗼𝗴𝘀 𝗱𝗶𝗳𝗳𝗲𝗿 𝗴𝗿𝗲𝗮𝘁𝗹𝘆 𝗳𝗿𝗼𝗺 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲