Verified Agile Explained
-Verified Agile Explained
The workflows that make up a verified agile process are not that different from the standard set you find in an OOTB agile implementations – with the twist being that technology now allows us to take our implementations to a merit-based, global team instead of being limited by proximity.  In my experience, it is always better to follow the agile doctrine strictly, and have each of your people and your customer sitting in the same room focused on the same topic.  In this age of constant connectivity and a flattened world, that just isn’t the way that people live their lives.  So here at HotWax Media, we’ve made accommodations to give both out customers and employees what they want: the additional flexibility to be where they need to, but not have their project skip a beat!
Agile’s proximity dogma is _the_ problem that geographically disparate teams have been battling with for years – but we are just now arriving at an era where our technical innovation, practice and patience have allowed us to reap the benefits of agile development methodologies across the globe.  In order to be able to offer our services to people all around the world, and still provide the level of quality and responsiveness that we’ve come to expect as professionals, we have added both additional processes and tools to agile workflows that ensure that we are on track and let us know exactly when we stray.
In my next sets of posts, I will start by digging into the details that define our verified agile workflows and processes as well as showing you how leveraging different nodes of a collaboration platform can make life easier on you and your customers.

 

In a continuation of my posts about Ecommerce ERP and our Verified Agile Process, managing your project to completion the way that HotWax Media does, I am going to dig into exactly what we mean by Verified Agile Process.

The workflows that make up a verified agile process are not that different from the standard set you find in a standard agile implementations – with the twist being that technology now allows us to take our implementations to a merit-based, global team instead of being limited by proximity.  In my experience, it is always better to follow the agile doctrine strictly, and have each of your people and your customer sitting in the same room focused on the same topic.  In this age of constant connectivity and a flattened world, that just isn’t the way that people live their lives.  So here at HotWax Media, we’ve made accommodations to give both our customers and employees what they want: the additional flexibility to be where they need to, but not have their project skip a beat!

Agile’s proximity dogma is THE problem that geographically disparate teams have been battling with for years – but we are just now arriving at an era where our technical innovation, practice and patience have allowed us to reap the benefits of agile development methodologies across the globe.  In order to be able to offer our services to people all around the world, and still provide the level of quality and responsiveness that we’ve come to expect as professionals, we have added both additional processes and tools to agile workflows that ensure that we are on track and let us know exactly when we stray.

In my next sets of posts, I will start by digging into the details that define our verified agile workflows and processes as well as showing you how leveraging different nodes of a collaboration platform can make life easier on you and your customers.

-Tim

Tim Ruppert is Chief Operating Officer at HotWax Media, an OFBiz service provider, as well as an OFBiz project committer and active community member. Tim will join other HotWax Media employees and advisors in periodically posting thoughts here related to OFBiz, eCommerce, ERP, and related topics.


DATE: Sep 14, 2010
AUTHOR: HotWax Systems
OFBiz Tutorial, Verified Agile Process, agile workflows, workflows, verified agile workflows, Enterprise ERP, Tim Ruppert, Open Source ERP, Education