Agile SE Part Two: What’s Your Problem?
Agile reduces reliance on requirements and emphasizes understanding and meeting stakeholder needs. What does that look like?
Agile reduces reliance on requirements and emphasizes understanding and meeting stakeholder needs. What does that look like?
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.
You’re probably familiar with the ConOps, learn about its little brother, the OpsCon. An OpsCon is a valuable SE artifact that can contribute to the success of your system development effort.
Diversity and inclusion means making sure that teams are actually diverse, across a range of visible and not-visible features. Why does that matter?
“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.
Human performance is a major factor in overall system performance and humans are increasingly the bottleneck for system performance. Human factors engineering design drives human performance and thus system performance.
The term ergonomics was coined by Wojciech Jastrzębowski in 1857 to mean “the science of work” with the goal of improving productivity and profit. He described the importance of physical, emotional, entertainment, and rational aspects of the labor and employee experience, but the context was squarely on factory-type production. Over time, this has evolved into two, slightly different definitions.
Human factors engineering (HFE) is a broad and multidisciplinary field that designs and evaluates the human interfaces of a system. That definition masks a lot of complexity, let’s explore the nuances.
UX is very much a type of human factors. UX extends the scope of consideration beyond the product itself to any interface which might affect the user’s perceptions and feelings of the product. Yet, the goal is the same: understand the human’s needs in order to design interfaces that meet them.
The US Department of Defense is overhauling it’s acquisition policy from a stale, process-driven approach to a new, outcome-driven approach. The new concept is called the Adaptive Acquisition Framework (AAF). Its goal is to remove bureaucracy and give government program managers more flexibility to adapt to the needs of their particular acquisition.