| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Stop wasting time looking for files and revisions. Connect your Gmail, DriveDropbox, and Slack accounts and in less than 2 minutes, Dokkio will automatically organize all your file attachments. Learn more and claim your free account.

View
 

Sotware Engineering in the 21st Century (Alistair Cockburn)

Page history last edited by Gordon Cloke 11 years, 8 months ago

March 17th 2009, 2:30pm

 

Session by Alistair Cockburn

 

Presentation is posted here: http://alistair.cockburn.us/Software+engineering+in+the+21st+century.ppt

 

Add your notes, aha's and take-aways below:

Comments (8)

Simon Roberts said

at 11:31 am on Mar 17, 2009

Visibility and light everywhere - Eric Gamma

Gordon Cloke said

at 11:45 am on Mar 17, 2009

People learn skills in a 3 stage progression: Shu / Ha / Ri
* Shu Follow (Learn a technique)
* Ha Break away (collect techniques)
* Ri Fluent (Blend techniques)

Gordon Cloke said

at 11:47 am on Mar 17, 2009

In the 21st century, software engineering will use:
* Craft (Shu-ha-ri progression)
* Cooperative game strategies (invention and communication)
* Lean processes (continuous flow, theory of constraints)

Generic Account said

at 12:49 pm on Mar 17, 2009

Communication slide could use a 3rd axis - reflecting one-one, many-one, one-many to best consider the communication type that makes the best fit for the situ.

Bernd Schiffer said

at 1:23 pm on Mar 17, 2009

aha effect: "unvalidated decisions = inventory" (which would be muda in lean context, then)

Gordon Cloke said

at 2:15 pm on Mar 17, 2009

It would be great to have a link to the slides presented today added to this page - if they are posted at alistair.cockburn.us, they are not immediately easy to find. Thanks!

Philippe Kruchten said

at 2:47 pm on Mar 17, 2009

I am missing an ethical component in Alistair's 21st century definition of software engineering, beyond "amicability". Much software development so far has been under the premises of "whatever we can get away with" (like finances?). Were do we see professional responsibility and not just to our peers?

Additional pointers for A. Cockburn:

R. Riehle: An Engineering Context for Software Engineering. Ph.D. thesis, 2008
http://theses.nps.navy.mil/08Sep_Riehle_PhD.pdf
Brief overview here: http://delivery.acm.org/10.1145/1470000/1467257/p24-denning.html?key1=1467257&key2=9755237321&coll=GUIDE&dl=GUIDE&CFID=27123691&CFTOKEN=81646047

P. Kruchten: Putting the engineering into software engineering.
http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=1290452

tjklatt said

at 6:40 am on Mar 21, 2009

my AHAs:
* Agile teams implementing, delivering and maintaining an IT/SOA/network solution perform like a J A Z Z band on stage
* Amicability: enjoyable ... standups with regularly visiting area product owners, scrum of scrums with rotating team delegates, scrum master sync, architecture sync, line manager sync, product owner sync, meta scrum, area product owners demo the readily specified (and maybe simulated, BPM) user stories to teams at sprint planning
* SW engineers in 21st century use Wii-Remotes to compose their systems ;)
Thoralf

You don't have permission to comment on this page.