Comments on: Musing about Agile http://confusedofcalcutta.com/2007/01/29/musing-about-agile/ a blog about information Mon, 06 Feb 2012 01:37:12 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Scott Rosenberg's Wordyard » Blog Archive » Blog responses to Dreaming in Code http://confusedofcalcutta.com/2007/01/29/musing-about-agile/comment-page-1/#comment-100053 Scott Rosenberg's Wordyard » Blog Archive » Blog responses to Dreaming in Code Wed, 14 Feb 2007 00:13:37 +0000 http://confusedofcalcutta.com/2007/01/29/musing-about-agile/#comment-100053 [...] From JP Rangaswami: If you're interested in software development, you should read the book. [...] [...] From JP Rangaswami: If you’re interested in software development, you should read the book. [...]

]]> By: Mohan http://confusedofcalcutta.com/2007/01/29/musing-about-agile/comment-page-1/#comment-94833 Mohan Sat, 03 Feb 2007 17:19:57 +0000 http://confusedofcalcutta.com/2007/01/29/musing-about-agile/#comment-94833 Interesting viewpoing "Customers don’t want software, they want the things they can make and do because of the software." This said, software is not just about customers.. It is also about enabling businesses to help their customers. I guess I am talking about the non-sexy Electronic Data Processing needs where the requirements for, say payroll processing or accounts receivable are well laid out and just needs to be done. Bulk of such work need not be agile, eh? Interesting viewpoing “Customers don’t want software, they want the things they can make and do because of the software.”

This said, software is not just about customers.. It is also about enabling businesses to help their customers.

I guess I am talking about the non-sexy Electronic Data Processing needs where the requirements for, say payroll processing or accounts receivable are well laid out and just needs to be done. Bulk of such work need not be agile, eh?

]]> By: Justin Brister http://confusedofcalcutta.com/2007/01/29/musing-about-agile/comment-page-1/#comment-93129 Justin Brister Wed, 31 Jan 2007 19:48:30 +0000 http://confusedofcalcutta.com/2007/01/29/musing-about-agile/#comment-93129 Phil, I agree, adding something about self-documenting code would be good. I think that Design by Contract is kind of covered by the Test Driven Development (contract between actor and component). I guess that from an architectural perspective, contracts between internal interfaces is important, and I guess something about high internal cohesion and low external coupling could also be included. I will have a go at refining this when I get the time. Phil,

I agree, adding something about self-documenting code would be good. I think that Design by Contract is kind of covered by the Test Driven Development (contract between actor and component). I guess that from an architectural perspective, contracts between internal interfaces is important, and I guess something about high internal cohesion and low external coupling could also be included.

I will have a go at refining this when I get the time.

]]> By: James Governor http://confusedofcalcutta.com/2007/01/29/musing-about-agile/comment-page-1/#comment-93070 James Governor Wed, 31 Jan 2007 16:14:08 +0000 http://confusedofcalcutta.com/2007/01/29/musing-about-agile/#comment-93070 we have done some work thinking about the smell of agile lately http://www.redmonk.com/cote/2006/12/05/the-smells-of-agile/ just a slightly different perspective. the user is king, but needs to be crowned by the developer, not the sales or marketing department. http://www.redmonk.com/jgovernor/2007/01/26/on-software-requirements-just-say-no-agile-is-simple/ an interesting tension between Extreme's YAGNI (you aren't going to need it), and user-driven adoption, with flow. we have done some work thinking about the smell of agile lately
http://www.redmonk.com/cote/2006/12/05/the-smells-of-agile/

just a slightly different perspective. the user is king, but needs to be crowned by the developer, not the sales or marketing department.

http://www.redmonk.com/jgovernor/2007/01/26/on-software-requirements-just-say-no-agile-is-simple/

an interesting tension between Extreme’s YAGNI (you aren’t going to need it), and user-driven adoption, with flow.

]]> By: Phil http://confusedofcalcutta.com/2007/01/29/musing-about-agile/comment-page-1/#comment-92998 Phil Wed, 31 Jan 2007 11:59:35 +0000 http://confusedofcalcutta.com/2007/01/29/musing-about-agile/#comment-92998 Justin, I think your first stab is good.... and similar to the set I dreamt up in my head. I would be inclined to add something about documentation in code to be just good enough. Almost a Design by Contract model. External Communication is also important, but must not be a burden. Phil Justin,
I think your first stab is good…. and similar to the set I dreamt up in my head.
I would be inclined to add something about documentation in code to be just good enough. Almost a Design by Contract model. External Communication is also important, but must not be a burden.
Phil

]]> By: Justin Brister http://confusedofcalcutta.com/2007/01/29/musing-about-agile/comment-page-1/#comment-92449 Justin Brister Tue, 30 Jan 2007 14:49:52 +0000 http://confusedofcalcutta.com/2007/01/29/musing-about-agile/#comment-92449 Had a quick stab at the Joel Test; http://jbrister.blogspot.com/2007/01/agile-joel-test.html Had a quick stab at the Joel Test;

http://jbrister.blogspot.com/2007/01/agile-joel-test.html

]]> By: Justin Brister http://confusedofcalcutta.com/2007/01/29/musing-about-agile/comment-page-1/#comment-92423 Justin Brister Tue, 30 Jan 2007 14:28:12 +0000 http://confusedofcalcutta.com/2007/01/29/musing-about-agile/#comment-92423 Funnily enough, I have been musing on pretty much the same thing, although maybe from a different angle; http://jbrister.blogspot.com/2007/01/to-agile-and-beyond.html I see Agile evolving to push more and more of the responsibility to the user, through concepts such as Service Factories. I am still trying to define what these Service Factories might look like and how they would work. I see users being able to create their own solutions on top of a virtualised delivery platform, without needing any specialist technical knowledge. Re: The Joel Test, I can see changing this to talk about build every compile, tests driving development etc. I might spend some time on this, as it could be a useful litmus test for our development teams. Funnily enough, I have been musing on pretty much the same thing, although maybe from a different angle;

http://jbrister.blogspot.com/2007/01/to-agile-and-beyond.html

I see Agile evolving to push more and more of the responsibility to the user, through concepts such as Service Factories. I am still trying to define what these Service Factories might look like and how they would work. I see users being able to create their own solutions on top of a virtualised delivery platform, without needing any specialist technical knowledge.

Re: The Joel Test, I can see changing this to talk about build every compile, tests driving development etc. I might spend some time on this, as it could be a useful litmus test for our development teams.

]]>