http://shapingsoftware.com/2008/05/12/user-business-and-tech/ Patterns and Practices for Software Success. Sat, 04 Feb 2012 12:25:23 +0000 http://wordpress.org/?v=2.7.1 hourly 1 http://shapingsoftware.com/2008/05/12/user-business-and-tech/comment-page-1/#comment-114 Shifts of Power Mon, 09 Jun 2008 07:50:29 +0000 http://shapingsoftware.com/2008/05/12/user-business-and-tech/#comment-114 [...] User, Business, and Tech One Comment, Comment or Ping [...] [...] User, Business, and Tech One Comment, Comment or Ping [...]

]]> http://shapingsoftware.com/2008/05/12/user-business-and-tech/comment-page-1/#comment-112 User Requirements vs. System Requirements Mon, 09 Jun 2008 07:49:04 +0000 http://shapingsoftware.com/2008/05/12/user-business-and-tech/#comment-112 [...] User, Business, and Tech No Comments, Comment or Ping [...] [...] User, Business, and Tech No Comments, Comment or Ping [...]

]]> http://shapingsoftware.com/2008/05/12/user-business-and-tech/comment-page-1/#comment-72 Requirements Types Sun, 01 Jun 2008 00:38:14 +0000 http://shapingsoftware.com/2008/05/12/user-business-and-tech/#comment-72 [...] User, Business, and Tech No Comments, Comment or Ping [...] [...] User, Business, and Tech No Comments, Comment or Ping [...]

]]> http://shapingsoftware.com/2008/05/12/user-business-and-tech/comment-page-1/#comment-42 JD Wed, 14 May 2008 02:53:38 +0000 http://shapingsoftware.com/2008/05/12/user-business-and-tech/#comment-42 The operations perspective is definitely key. It's a living, breathing system. As one of my mentors would say -- "it's got lungs." The operations perspective is definitely key. It’s a living, breathing system. As one of my mentors would say — “it’s got lungs.”

]]> http://shapingsoftware.com/2008/05/12/user-business-and-tech/comment-page-1/#comment-41 Alik Levin | PracticeThis.com Mon, 12 May 2008 10:39:08 +0000 http://shapingsoftware.com/2008/05/12/user-business-and-tech/#comment-41 I have a similar approach, the only diff is that I see IT folks as an end users too. These guys are responsible for supporting the app/solution in prod environment, they are the first one who's flamed by end users, they are those who under fire when shit happens and hits the fan. That is why I think DFO (design for operations) or as I like to call it ODL (operations development lifecycle) must be practiced just like SDL and PDL. I have a similar approach, the only diff is that I see IT folks as an end users too. These guys are responsible for supporting the app/solution in prod environment, they are the first one who’s flamed by end users, they are those who under fire when shit happens and hits the fan. That is why I think DFO (design for operations) or as I like to call it ODL (operations development lifecycle) must be practiced just like SDL and PDL.

]]>