Agile and distributed CVS share the same philosophy of incremental
changes -- looks obvious but requires a bunch of conditions to be effective:
1- documentation: each fork lives like a sub-project
2- quick build: ship testable releases as soon as possible ("Daily
Builds Are Your Friend" by Joel Spolsky,
http://www.joelonsoftware.com/articles/fog0000000023.html)
3- isolation: being able to compile with or without a given feature
without any side effect
We're working on that almost daily at FoxInCloud, our release process is
now fully automatic, including sending release notification to
registered users (beta testers adn/or regular users).
Thierry Nivelet
FoxInCloud
Give your VFP app a second life in the cloud
http://foxincloud.com/
Le 05/01/2016 16:18, Stephen Russell a écrit :
Agile is small iterative sprints to get the job done instead of waterfall
where you deliver the whole ball of wax as a finished product.
This is all about being able to say hold on for now, we are working for
another group who waited while we make version 1 for you.
On Tue, Jan 5, 2016 at 1:28 AM, Thierry Nivelet <[email protected]>
wrote:
SemVer (http://semver.org/) also helps understanding how to phase new
features, enhancements and fixes; a little complicated though (eg version
2.21.0-beta.7)
Thierry Nivelet
FoxInCloud
Give your VFP app a second life in the cloud
http://foxincloud.com/
Le 04/01/2016 17:30, Dave Crozier a écrit :
Stephen,
It appears that in this scenario which I have seen on many occasions,
that all development "changes" should be immediately frozen or the job
becomes a moving target that will never get completed successfully no
matter how many resources are thrown at it. In addition, you need a good
project manager who understands the "whole project" in its entirety and who
can assess the knock on effects that delays and changes can have. I think
it is called "experience"!! <smile>
Having frozen any changes and generated an aiming point for "phase 1"
then a subsection of the overall project should be identified which is
complete in its entirety and can be completed using the minimum changes to
peripheral systems.... We now know this methodology as "Agile" development
but it is no different to how I was taught in the 70's.... you just need
less people to do it because the age old hierarchy of junior programmer,
programmer, systems analyst, consultant no longer exists as they are all
contained under the name "developer".
Dave
-----Original Message-----
From: ProFox [mailto:[email protected]] On Behalf Of Stephen
Russell
Sent: 04 January 2016 16:17
To: ProFox Email List <[email protected]>
Subject: [NF] Do you monitor Demand requests for your services?
https://tinyletter.com/programming-beyond-practices/letters/the-sad-graph-of-software-death
--
Stephen Russell
Sr. Analyst
Ring Container Technology
Oakland TN
901.246-0159 cell
--- StripMime Report -- processed MIME parts --- multipart/alternative
text/plain (text body -- kept)
text/html
---
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
