Comments for Pragmatic Jim http://pragmaticjim.wordpress.com Software Development with a Pragmatic Edge Tue, 09 Oct 2007 09:03:37 +0000 http://wordpress.com/ hourly 1 Comment on An Agile Culture by pragmaticjim http://pragmaticjim.wordpress.com/2007/10/05/an-agile-culture/#comment-3 pragmaticjim Tue, 09 Oct 2007 09:03:37 +0000 http://pragmaticjim.wordpress.com/2007/10/05/an-agile-culture/#comment-3 Thanks for your comment. Well, yes I would agree - you need to be a good programmer too, if we look at this for a developer. My idea behind this article agile thinking really is to get it across to the whole project team - team manager, developer, tester, requirements engineer, architect. Of course, you need to be good at your project function to succeed at all. And it's a good point on continuous testing - maybe that should get top priority :-) Thanks for your comment.

Well, yes I would agree – you need to be a good programmer too, if we look at this for a developer.

My idea behind this article agile thinking really is to get it across to the whole project team – team manager, developer, tester, requirements engineer, architect.
Of course, you need to be good at your project function to succeed at all.

And it’s a good point on continuous testing – maybe that should get top priority :-)

]]> Comment on An Agile Culture by Misha Peric http://pragmaticjim.wordpress.com/2007/10/05/an-agile-culture/#comment-2 Misha Peric Mon, 08 Oct 2007 18:37:15 +0000 http://pragmaticjim.wordpress.com/2007/10/05/an-agile-culture/#comment-2 I think that Agile thinking is great. But don’t you think that if you embrace Agile thinking before you become good programmer can be devastating? Agile thinking is like using an IDE, it enables anyone to produce working betas easily, but without knowing what’s going on behind the scene you will not go beyond betas anytime soon. Btw isn’t continues testing the main concept of Agile thinking that makes it actually really usable in reality? Giving up on features, changing the direction, communicating and releasing early is easy, even interesting … forcing yourself to continually test the app is not! And I think very bad things happen when you use all Agile concepts but testing! I think that Agile thinking is great. But don’t you think that if you embrace Agile thinking before you become good programmer can be devastating? Agile thinking is like using an IDE, it enables anyone to produce working betas easily, but without knowing what’s going on behind the scene you will not go beyond betas anytime soon.

Btw isn’t continues testing the main concept of Agile thinking that makes it actually really usable in reality?

Giving up on features, changing the direction, communicating and releasing early is easy, even interesting … forcing yourself to continually test the app is not!

And I think very bad things happen when you use all Agile concepts but testing!

]]>