DevOps Zone is brought to you in partnership with:

Dennis Doomen

Dennis is Principal Consultant at Aviva Solutions, speaker, author, coach, specialized in ALM, TDD, DDD, design patterns, architecture, Agile, TFS and Silverlight. He published coding guidelines for C#3.0 and C#4.0 and maintains multiple open-source .NET projects. You can tweet him at @ddoomen Dennis is a DZone MVB and is not an employee of DZone and has posted 35 posts at DZone. You can read more from them at their website. View Full User Profile

ALM Practices Every Developer Should Know About

06.01.2011

| 8030 views |

Related MicroZone Resources

Beyond the Buzzwords: Continuous Delivery & DevOps

Continuous Delivery Maturity Model

Learn The Basics of Deployment Automation

Why DevOps? Why Now?

1K FREE Pre-Built Configs

Like this piece? Share it with your friends:

| More

So now that I’ve finished my multi-part post on getting the most out of user stories, it is time to provide a nice convenient overview of some essential practices that I’ve blogged about. I don’t have any additional parts planned, but if I come up with something new, I’ll make sure this list is updated.

References

Reference:

ALM Practices Every Developer Should Know About

Published at DZone with permission of Dennis Doomen, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)

Tags:

Comments

Kathy John replied on Tue, 2012/02/21 - 1:11pm

It's always a good idea to speak the language of the clients.
Keeping a list of words and there meaning, can also get new people on the project up to speed very quickly.
The list also comes in handy when constructing a domain model, because a domain model also functions as a common language between developer and client.