The Illusion of Requirements; the Requirements Myth
“Requirements” is a pre-agile construct based on our false belief that building software was somehow like the construction of buildings.
“Requirements” is a pre-agile construct based on our false belief that building software was somehow like the construction of buildings.
Hi. I have come to love Pair Programming. I enjoy the collaboration, cross-training, and better solutions that emerge while I pair.
In my software development practice, I rely on several techniques for increasing the probability of success with a pairing relationship.
Since pairing is a relational practice relying on imperfect communication, misunderstandings and slights can emerge.
There are several ways in which Sustainable Software Development has evolved from Extreme Programming (XP)
If you are using Grounded Theory to conduct research in software engineering, I would love to hear from you. Please contact me at [professor at gmail.com]
If you are starting out on grounded theory research, I would suggest this plan of action:
See the list of software development wastes or read this ICSE paper
We Know the Way - Phonetic Lyrics - Moana
2002 | 2003 | 2006 | 2011 |
---|---|---|---|
Requirements | Partially Done Work | Work in Progress | |
Extra Steps | Extra Processes | Relearning | Technical Debt |
Extra Features | |||
Handoffs | Task Switching | Handoffs | Handovers |
Delays | |||
Finding Information | Motion | Task Switching | |
Defects Not Caught by Tests | Defects |