Archive for category Agile
Coffee Notes: The Domain Test Values Class
Posted by cgrant in Agile, Java, Technology on January 13, 2011
Here’s an interesting clip on optimizing the way you write Unit tests. In his Blog entry, Dave Bower presents a pattern for using meaningful terminologies rather than literals in your tests.
http://manbuildswebsite.com/2010/12/20/domain-test-values/
While literals are typically a code smell in stadard coding, I personally have seen quite a few in unit tests. Applying the solid coding practices Brower presents will make your tests easier to read and maintain.
Whats on Your Book Shelf – Agile
Posted by cgrant in Agile, Technology on January 12, 2011
So one thing I always find intersting is hearing about what everyone has on their bookshelf. So I thought I’d provide a list of some really good books I’ve been devouring recently, and hopefully hear back on what you all are reading.
Drop a comment with what’s on your bookshelf?
Here are some Agile books I’ve been reading recently. Read the rest of this entry »
Coffee Notes: Negotiating Scrum Through Watefall
Posted by cgrant in Agile, Coffee Notes, Management, Technology on January 10, 2011
Here’s an interesting article about how to really deal with many of the challenges faced when dealing with Waterfall cultures and new Agile concepts. In his article Phil Southward lists out many of the key SDLC phases as well as how Agile teams can work through them in a wartefall organization. qaheaven (@qaheaven)10/21/10 2:38 AM Negotiating #Scrum Through a Waterfallhttp://bit.ly/aE86Zt |
http://www.scrumalliance.org/articles/189-negotiating-scrum-through-a-waterfall
Unit Testing Real Code
Posted by cgrant in Agile, Development, Java, Technology on January 8, 2011
Quality code is important, we all know that. In some way or another developers work to ensure their is tested. We code something then try it out. Maybe check the database, or look at the UI what ever is needed to let us know it worked. As we build up our solution maybe we change our design a bit to make it cleaner or more robust, or just extend it to add a new feature. At some point in this process something we built before will inevitable break. Then we re run our tests and try to find the bug. Unit tests are a great way to help ensure quality code, but developers new to unit testing are often faced with the daunting task of testing mammoth legacy code. Where to start, how to do it right, how to stay sane… Read the rest of this entry »
Continuous Delivery through Latent Code, Feature Bits, Dormancy
Posted by cgrant in Agile, Development, Technology on November 20, 2010
Continuous delivery is the concept of regularly producing output rather than building up a series of changes for one big release. To simplify the idea, think about monthly release of a project rather than one major release at the end. While we may like to think we are the only one coding in an application, that’s not the case. By leaving code in a state where it can’t go into product we lock up the release and add risk to all the other initiatives trying to go into production. A better practice is to use latent code and feature bits to make your code dormant, thus reducing risk and continuously deliver value. Lets look at some of the techniques.
-
You are currently browsing the archives for the Agile category.
Shared on Google Reader- Working with Git - Part 1 - Our initial experience
- Jenkins: The Definitive Guide
- A Google-a-Day Puzzle for Monday, June 13th
- Creating a Code 39 Barcode using HTML, CSS and Javascript
- Tech Comics: "The Busy Coder"
- Laws of Software Design
- Unit Test Patterns: The Domain Test Values Class
- Spring & JUnit - What you Don't Know
- 15 Lightweight and Minimal CSS Frameworks
- Should Schools Go Back to 1983 Technology?
