-
Notifications
You must be signed in to change notification settings - Fork 90
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
WIP: Initial skeleton with references and key bullets (#1341)
- Loading branch information
1 parent
249f6e2
commit e734325
Showing
1 changed file
with
40 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
# Myth of Developer Productivity | ||
|
||
<!--deck text start--> | ||
The ability to directly effectively measure individual software developer productivity has eluded software developers for decades. Why is this so hard and what are the alternatives? | ||
<!--deck text end--> | ||
|
||
#### Contributed by [Roscoe A. Bartlett](https://github.com/bartlettroscoe), [Mark C. Miller](https://github.com/markcmiller86) | ||
|
||
#### Publication date: December, ??? 2022 | ||
|
||
Here are the references I want to include: [myth-dev-prod], [cant-meas-prod], [kanban-and-scrum], [impl-lean-dev] (NOTE: We need a CC article for [impl-lean-dev].) | ||
|
||
Key points to make? | ||
|
||
* Why we care to measure productivity? => Software estimation, individual developer performance evaluation? | ||
|
||
* The number one way of improving productivity is to write less software (see [impl-lean-dev]). | ||
|
||
* The cost of software maintenance is often several times much higher than the cost to create the software in the first place. | ||
|
||
* The on-going cost of software maintenance is strongly correlated with the size of the code base (see: code complete???). | ||
|
||
* Defining productivity by directly measuring the amount of software created disincentivizes solutions that may reuse existing software or refactorings that may actaully result in less overall source code. | ||
|
||
* Cover some of the arguments made in the comments of https://github.com/betterscientificsoftware/bssw.io/issues/1341 | ||
|
||
<!--References--> | ||
|
||
[myth-dev-prod]: https://nortal.com/us/blog/the-myth-of-developer-productivity/ "The myth of developer productivity" | ||
[cant-meas-prod]: martinfowler.com/bliki/CannotMeasureProductivity.html "Cannot Measure Productivity" | ||
[kanban-and-scrum]: bssw.io/items/kanban-and-scrum-making-the-best-of-both "Kanban and Scrum: Making the best of both" | ||
[impl-lean-dev]: https://bartlettroscoe.github.io/reading-list/#implementing_lean_software_development_2007 "Implementing Lean Software Development" | ||
|
||
|
||
<!--- | ||
Publish: yes | ||
Pinned: no | ||
Topics: Software engineering, refactoring, design, peer code review | ||
RSS update: 2021-10-20 | ||
---> |