Some of you have heard the term “agile software development”, which refers to a process of software development based on frequent, iterative development. crowdSPRING has been applying the principles of agile development to our own software development efforts for the past year.
We were bogged down throughout much of 2009 launching new products in part because our thinking was too grand. As a result, we ran into too many roadblocks that require further discussion, research, debate, and planning. This caused us to be less effective – and delayed product launches and improvements.
About six months ago, we looked at our non-software development processes (business, strategy, finance, etc.) and wondered why we also couldn’t apply many of the same principles (of agility) to those processes.If you read the Principles behind the Agile Manifesto, you quickly realize that the same principles can apply to many things outside of software development.
About 6 months ago, we started applying principles of agility to everything we do. This has helped us immensely to streamline our processes, to reach quicker decisions, and to iterate our policies and practices much quicker than we had done in the past. We see clear advantages to this approach – I discuss some of these advantages in the following video.
subscribe via RSS
subscribe via e-mail
follow me on Twitter
find me on Linked-in
{ 1 comment… read it below or add one }
What is the opposite of Agile development? Is there another popular design pattern?
“Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.”
Can’t releasing software early cause many problems? like dissatisfied customers, poor first impressions, and support issues on software that will eventually change