× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



All projects should begin with their requirements in this case "Agile user stories".

These allow you to build software that meets the real needs of the users.
Since its their story to start with and not the "Chinese Whispers" or "Broken Telephone" games we all have seen at one point or another.

The 3 stages of Agile Planning.
Release Planning
Sprint Planning
Daily Planning

The daily planning is the Daily Standup or Daily Scrum huddle.
Great for knowing
What task the person committed to complete yesterday and where they stand.
What task they commit to do today.
What risk/roadblocks do they see that could stop today task from happening.

Quote......
The daily scrum is about snychronization, commitment, and
accountability. Each individual invites self and group inspection on
the work he or she has accomplished the previous day. This daily
ritual is an important input for team adaptation throughout the
sprint. This brief interlude for reflection and seeding the current
day's work is an essential component of Scrum.

This is very beneficial approach IMO.

Whether it is done with OO or RPG has nothing to do with it IMO.

I like it a lot more than jumping off the "waterfall" onto the unseen rocks.

Regards,
Bill Hopkins


Please email the following address
for EDI / Electronic interface support.
eCommerce@xxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: Wednesday, October 23, 2013 10:21 AM
To: Midrange Systems Technical Discussion
Subject: Re: Looking for Agile Experience

On 10/23/2013 9:11 AM, Richard Schoen wrote:
There appear to be shades of Agile, so we've picked up the bits that
seemed to make sense such as requirements before coding, but I don't
believe we are doing standups, sprints or pair programming.

IMO, the parts of agile that would benefit ANY team (regardless of how agile they go) are sprints and standups.

Pair programming, especially for experienced people, would only result in injury and death (and I'm only half kidding there).

david




--
IBM i on Power Systems: For when you can't afford to be out of business!

I'm riding a metric century (100 km / 62 miles) in the 2014 Chicagoland Tour de Cure to raise money for diabetes research, education, and advocacy. Sponsor me by visiting http://archive.ridewithdavid.com. Any amount is appreciated.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.