Comments on: Agile & Scrum Programming http://agileprogramming.org Learn all about scrum & agile programming Tue, 29 Nov 2011 20:36:51 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: admin http://agileprogramming.org/comment-page-1/#comment-8855 admin Tue, 25 Oct 2011 15:56:55 +0000 http://agileprogramming.org/?page_id=38#comment-8855 Here is a good whitepaper for you to read, "The ScrumMaster Checklist". http://www.open.collab.net/news/library/agile-whitepapers.html Here is a good whitepaper for you to read, “The ScrumMaster Checklist”.
http://www.open.collab.net/news/library/agile-whitepapers.html

]]> By: admin http://agileprogramming.org/comment-page-1/#comment-8854 admin Tue, 25 Oct 2011 15:52:59 +0000 http://agileprogramming.org/?page_id=38#comment-8854 You may be interested in reading this whitepaper "Intro to Agile". It describes what Agile is in more detail and how it can improve your organization. http://www.open.collab.net/news/library/agile-whitepapers.html This paper is written for IT managers and CXOs with an interest in improving development productivity. First comes an introduction to the two broad schools of thought common to software development: traditional sequential, a.k.a. "the waterfall method," and iterative methods, of which Agile is one subset. The objective is to demonstrate the shortcomings of the waterfall approach, while providing a solution in iterative and, more specifically, Agile methods. You may be interested in reading this whitepaper “Intro to Agile”. It describes what Agile is in more detail and how it can improve your organization.
http://www.open.collab.net/news/library/agile-whitepapers.html

This paper is written for IT managers and CXOs with an interest in improving development productivity. First comes an introduction to the two broad schools of thought common to software development: traditional sequential, a.k.a. “the waterfall method,” and iterative methods, of which Agile is one subset. The objective is to demonstrate the shortcomings of the waterfall approach, while providing a solution in iterative and, more specifically, Agile methods.

]]> By: ScrumDaddy http://agileprogramming.org/comment-page-1/#comment-8844 ScrumDaddy Mon, 24 Oct 2011 23:53:26 +0000 http://agileprogramming.org/?page_id=38#comment-8844 Customers have been asking me a lot lately about the overall benefits they can expect from Agile, in terms of hard, numbers that can be vetted and agreed upon by their finance teams. I always struggle with that though. The benefit of agile is more robust software with just the right “high value” features delivered in a more rapid timeframe. Agile has broken down some internal barriers - not only the barriers between the customer and the development team, but also internally between the development team and the business users. The focus on business value means the developers are working more closely with the business community, and vice versa. By bringing developers and business stakeholders together, it creates a more cohesive working environment, increased customer satisfaction and better software in a faster timeframe. One view I kind of like are looking at earned value metrics. Check out the white paper entitled Monitoring Scrum Project with AgileEVM and Earned Business Value (EBV) Metrics here: http://www.open.collab.net/news/library/agile-whitepapers.html Customers have been asking me a lot lately about the overall benefits they can expect from Agile, in terms of hard, numbers that can be vetted and agreed upon by their finance teams. I always struggle with that though. The benefit of agile is more robust software with just the right “high value” features delivered in a more rapid timeframe. Agile has broken down some internal barriers – not only the barriers between the customer and the development team, but also internally between the development team and the business users. The focus on business value means the developers are working more closely with the business community, and vice versa. By bringing developers and business stakeholders together, it creates a more cohesive working environment, increased customer satisfaction and better software in a faster timeframe.

One view I kind of like are looking at earned value metrics. Check out the white paper entitled Monitoring Scrum Project with AgileEVM and Earned Business Value (EBV) Metrics here: http://www.open.collab.net/news/library/agile-whitepapers.html

]]> By: Rohit Kumar Bhardwaj http://agileprogramming.org/comment-page-1/#comment-8793 Rohit Kumar Bhardwaj Thu, 20 Oct 2011 14:22:00 +0000 http://agileprogramming.org/?page_id=38#comment-8793 Thanks for sharing such informative article. Thanks for sharing such informative article.

]]> By: Jorge Merino http://agileprogramming.org/comment-page-1/#comment-7683 Jorge Merino Sun, 31 Jul 2011 16:10:24 +0000 http://agileprogramming.org/?page_id=38#comment-7683 Agile development is nice when everybody is applying it as they should, and when every once embraces the full filosophy behind. The problem is when people want to set a deadline but they continue adding changes to the stuff already done. It is nice to gather changes to have a product that works, what is not nice, is to have people that think that the can add features, request for endless changes or have other projects to work on but still keep the original deadline. Agile development is nice when everybody is applying it as they should, and when every once embraces the full filosophy behind.

The problem is when people want to set a deadline but they continue adding changes to the stuff already done.

It is nice to gather changes to have a product that works, what is not nice, is to have people that think that the can add features, request for endless changes or have other projects to work on but still keep the original deadline.

]]> By: Dont Care http://agileprogramming.org/comment-page-1/#comment-7481 Dont Care Tue, 12 Jul 2011 21:01:57 +0000 http://agileprogramming.org/?page_id=38#comment-7481 "Agile" would seem to require a total sign-off by all parties involved? Can't see my customers coming back again and again for "project reviews" after every "sprint". Can't see effective purchasing of hardware when requirements are constantly allowed to change mid-stream? Can't see ever being able to designate a go live date, when the customer is allowed to add new requirements that can totally shift the course of the project. In short, agile does NOT "reduce both development costs and time to market". The waterfall method may well end up yielding a product that isn't what the customer wants, but at least the project ends, and the costs/dates are known, and more importantly from the IT perspective "we gave the customer what they asked for" (which is not what they needed), which is particularly (defensible) important if your customer isn't in-house. The agile method with its never ending requirements trickle, can yield to hardware/license purchases that are inadequate (and need to be replaced), and a software development team that is always working on those "last few changes". “Agile” would seem to require a total sign-off by all parties involved? Can’t see my customers coming back again and again for “project reviews” after every “sprint”. Can’t see effective purchasing of hardware when requirements are constantly allowed to change mid-stream? Can’t see ever being able to designate a go live date, when the customer is allowed to add new requirements that can totally shift the course of the project. In short, agile does NOT “reduce both development costs and time to market”. The waterfall method may well end up yielding a product that isn’t what the customer wants, but at least the project ends, and the costs/dates are known, and more importantly from the IT perspective “we gave the customer what they asked for” (which is not what they needed), which is particularly (defensible) important if your customer isn’t in-house. The agile method with its never ending requirements trickle, can yield to hardware/license purchases that are inadequate (and need to be replaced), and a software development team that is always working on those “last few changes”.

]]> By: Cplex http://agileprogramming.org/comment-page-1/#comment-6887 Cplex Wed, 01 Jun 2011 11:56:16 +0000 http://agileprogramming.org/?page_id=38#comment-6887 Thanks for such a huge programming concept. I appreciate it......... ateji.com Thanks for such a huge programming concept. I appreciate it………

ateji.com

]]> By: atejip http://agileprogramming.org/comment-page-1/#comment-5543 atejip Fri, 14 Jan 2011 07:10:19 +0000 http://agileprogramming.org/?page_id=38#comment-5543 Really Impressive! Thanks for this info........ Really Impressive! Thanks for this info……..

]]> By: chetan http://agileprogramming.org/comment-page-1/#comment-5177 chetan Wed, 11 Aug 2010 05:36:59 +0000 http://agileprogramming.org/?page_id=38#comment-5177 this post gives the clear understanding about Agile Methodology this post gives the clear understanding about Agile Methodology

]]> By: MC http://agileprogramming.org/comment-page-1/#comment-5139 MC Wed, 14 Jul 2010 00:08:14 +0000 http://agileprogramming.org/?page_id=38#comment-5139 As a scrummaster, My biggest issue is to keep the team update the time tracking tool daily. Any idea how to motivate the team to update daily. As a scrummaster, My biggest issue is to keep the team update the time tracking tool daily. Any idea how to motivate the team to update daily.

]]>