From f3fe6aead1d16a824e350608f3c9c362078e0b13 Mon Sep 17 00:00:00 2001 From: Andy Ko Date: Tue, 26 Mar 2019 14:01:55 -0700 Subject: [PATCH] Fixed #22, citing Atlantic article. --- organizations.html | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/organizations.html b/organizations.html index f935393..c8162af 100644 --- a/organizations.html +++ b/organizations.html @@ -15,7 +15,6 @@ - Software engineering organizations @@ -23,7 +22,7 @@

Back to table of contents

- Credit: Andrew J. Ko + A software engineering team hard at work. Credit: Andrew J. Ko

Software organizations

Andrew J. Ko
@@ -34,7 +33,7 @@

Organizations are a much bigger topic than I could possibly address here. To deeply understand them, you'd need to learn about organizational studies, organizational behavior, information systems, and business in general.

-

The subset of this knowledge that's critical to understand about software engineering is limited to a few important concepts. The first and most important concept is that even in software organizations, the point of the company is rarely to make software; it's to provide value (Osterwalder et al. 2015). Software is sometimes the central means to providing that value, but more often than not, it's the information flowing through that software that's the truly valuable piece. Requirements, which will be discussed in more detail soon, help engineers organize how software will provide value.

+

The subset of this knowledge that's critical to understand about software engineering is limited to a few important concepts. The first and most important concept is that even in software organizations, the point of the company is rarely to make software; it's to provide value (Osterwalder et al. 2015). Software is sometimes the central means to providing that value, but more often than not, it's the information flowing through that software that's the truly valuable piece. Requirements, which we will discuss in a later chapter, help engineers organize how software will provide value.

The individuals in a software organization take on different roles to achieve that value. These roles are sometimes spread across different people and sometimes bundled up into one person, depending on how the organization is structured, but the roles are always there. Let's go through each one in detail so you understand how software engineers relate to each role. @@ -54,11 +53,11 @@

There are other roles you might be thinking of that I haven't mentioned:

-

Every decision made in a software team is under uncertainty, and so another important concept in organizations is risk (Boehm 1991). It's rarely possible to predict the future, and so organizations must take risks. Much of an organization's function is to mitigate the consequences of risks. Data scientists and researchers mitigate risk by increasing confidence in an organization's understanding of the market and its consumers. Engineers manage risk by trying to avoid defects and moving fast.

+

Every decision made in a software team is under uncertainty, and so another important concept in organizations is risk (Boehm 1991). It's rarely possible to predict the future, and so organizations must take risks. Much of an organization's function is to mitigate the consequences of risks. Data scientists and researchers mitigate risk by increasing confidence in an organization's understanding of the market and its consumers. Engineers manage risk by trying to avoid defects. Of course, as many popular outlets on software engineering have begun to discover, when software fails, it usually "did exactly what it was told to do. The reason it failed is that it was told to do the wrong thing." (Somers 2017).

Open source communities are organizations too. The core activities of design, engineering, and support still exist in these, but how much a community is engaged in marketing and sales depends entirely on the purpose of the community. Big, established open source projects like Mozilla have revenue, buildings, and a CEO, and while they don't sell anything, they do market. Others like Linux (Lee & Cole 2013) rely heavily on contributions both from volunteers (Ye & Kishida 2003), but also paid employees from companies that depend on Linux, like IBM, Google, and others. In these settings, there are still all of the challenges that come with software engineering, but fewer of the constraints that come from a for-profit or non-profit motive.

@@ -94,6 +93,8 @@

A. Osterwalder, Y. Pigneur, G. Bernarda, & A. Smith (2015). Value proposition design: how to create products and services customers want. John Wiley & Sons.

+

Somers, James (2017). The Coming Software Apocalypse. The Atlantic Monthly.

+

Yunwen Ye and Kouichi Kishida. 2003. Toward an understanding of the motivation Open Source Software developers. In Proceedings of the 25th International Conference on Software Engineering (ICSE '03). IEEE Computer Society, Washington, DC, USA, 419-429.