tag:blogger.com,1999:blog-10280668.post115299994870212655..comments2023-09-22T06:05:17.495-05:00Comments on Brad Appleton's ACME Blog: The 5C's of Agile SCMBrad Appletonhttp://www.blogger.com/profile/15136106921504315995noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-10280668.post-1154015436451214022006-07-27T10:50:00.000-05:002006-07-27T10:50:00.000-05:00Hi Frank and Dave! Thanks for the comments.Dave, I...Hi Frank and Dave! Thanks for the comments.<BR/><BR/>Dave, I very much like your idea of <I>Continuity</I>. I think it relates to "availability" as I referred to it in a subsequent blog entry on <A HREF="http://blog.bradapp.net/2006/07/codeline-flow-availability-and.html" REL="nofollow">codeline flow, availability and throughput</A>. I think Frank is perhaps getting at the same think when he writes of "Continuous Clarity."<BR/><BR/>Frank, regarding "complete" being perhaps more "big-up-front" than "agile", I think that's not a problem the way I described it because it's more about being holistic or "whole" as opposed to parts (e.g., preferring full-builds to partial builds, and running all the tests over partial-testing).<BR/><BR/><I>Complete</I> in this context means "whole" rather than "done" or "all up-front" (perhaps <I>Completeness</I> is slightly better at indicating the meaning of both "necessary" *and* "sufficient").Brad Appletonhttps://www.blogger.com/profile/15136106921504315995noreply@blogger.comtag:blogger.com,1999:blog-10280668.post-1153378976696040792006-07-20T02:02:00.000-05:002006-07-20T02:02:00.000-05:00Excellent idea! I've thought of a few other ones:-...Excellent idea! I've thought of a few other ones:<BR/><BR/>- Constant Change, or Continuous Change<BR/>- Collaborative Communication<BR/>- "Clockwork Cycles" instead of Cadence<BR/>- Clarity of Configurations, or Clear Configurations<BR/><BR/>Consistency and Completeness may be considered as attributes of Correctness. I propose to make it one.<BR/><BR/>Completeness is even arguable, as Agile means we strive for minimum, sufficient and necessary functionality<BR/><BR/>Clarity of Configurations means that it must be simple and understandable which configurations are where, and what is in it. Beit workspaces (sandboxes), test systems, proto rigs or production systems, it must be clear and simple to be Agile.Anonymoushttps://www.blogger.com/profile/05338420995938912564noreply@blogger.com