A fighter jet isn’t a smartphone… but it could be
Fighter jets and cell phones are both hardware-enabled, software-defined systems, but that’s about where the similarities end. Maybe they have more in common than we think.
Category: Software Engineering
Written in Blood: Case Studies of Systems Engineering Failure
Our world and our systems are safer than ever. A major reason why is that we’ve learned from prior mistakes. Many of our practices, rules, and standards are “written in blood” from past, tragic failures. We learn so that we don’t repeat the same mistakes. Of course, we first identify the proximate causes—the specific events directly leading to a casualty. To truly learn, we must take a step back to examine the larger context: what were the preceding holes in the Swiss cheese, and how do we account for them in our systems engineering practice? This approach is increasingly important …
Written in Blood: Case Studies of Systems Engineering Failure Read more »
Minimum Viable Product (MVP): You’re doing it wrong
The concept is simple: create a version of your solution that’s just good enough and put it out in the real world to validate assumptions about the product and market. That way, if your assumptions are wrong, you can pivot or shut it down without having spent too many resources on a failed idea. If your assumptions are right, you’ll have some great feedback to propel you along and help populate your product roadmap.
The term is often misapplied. Learn what an MVP is, what it isn’t, and how to leverage them for the success of your concept.
Agile isn’t faster
A common misconception is that Agile development processes are faster. I’ve heard this from leaders as a justification for adopting Agile processes and read it in proposals as a supposed differentiator. It’s not true. Nothing about Agile magically enable teams to architect, engineer, design, test, or validate any faster.
Agile SE Part One: What is Agile, Anyway?
Agile is a relatively new approach to software development based on the Agile Manifesto and Agile Principles. This overview prepares us to dive into how we can apply this approach to systems engineering.
Agile SE Part Zero: Overview
“Agile” is the latest buzzword in systems engineering. It has a fair share of both adherents and detractors, not to mention a long list of companies offering to sell tools, training, and coaching. Dive into a thoughtful, reasoned discussion about when and how agile can work for systems engineering projects.
Using Agile on Traditional Government Contracts
Say you’re standing up a software development team. You really like the agile approach, but your customer didn’t read my previous post about agile contracts. Can you still use agile or are you stuck developing a waterfall-based program plan?
Agile Government Contracts
Agile promises to deliver capabilities to the end user faster and more effectively. Government project offices can realize the benefits, but must carefully design their contracts to support the agile approach. A growing body of expertise, lessons learned, and acquisition resources are available to help make it happen.