Lesson Learned: It’s faster, cheaper, and easier to develop high-quality software when teams follow a recommended process and actively manage risks.
Risk:
Not following a recommended process or neglecting risk management leads to software with more defects and longer timelines. For instance, skipping risk management might result in a critical defect surfacing late in development. Fixing it at that stage could triple the cost and delay delivery by months.
A naïve project plan that underestimates the difficulty of developing defect-free embedded system software will often fall short. To an inexperienced planner, a realistic schedule may seem unrealistic, but the fastest, easiest, and cheapest way to the finish line is to follow the process and have a realistic plan.
Key Questions to Ask:
- What software development process is the team following? There should be a written process in place. If you don't have your own, borrow someone else's and tweak it for your situation.
- Who is the embedded software architect? Are they Qualified, Competent, and Capable (QCC)? Without an empowered QCC architect and architecture, your project will take longer.
- Has the team addressed and resolved the risks in the Project Risk Management checklist? (This checklist contains critical items for project success. While addressing all risks doesn’t guarantee success, neglecting them almost certainly ensures failure.)
Takeaway
Respecting the process and adopting a realistic approach to planning are your strongest tools for delivering "fast, cheap, and easy" software. Cutting corners upfront can cost you later on.
Comments
Post a Comment