-
Detailed Estimation Sucks
Pretend you have a team cranking away at a production app. Part of the IT staff, so to speak. Please have a seat. Yes, over there by the window is fine. Buckle up. You may experience some turbulence. If you want to know "when you can get all that
Last updated:
Apr 20 2010, 10:29 PM EDT by
-
Writing Good Bugs
Most of the instructions for Writing Good Issues still apply! Meaningful title Indicate what is wrong Example: "BOP Application" as a title is too wide open to interpretation. One tip is to think of being in your user's/client's shoes and
Last updated:
Apr 30 2010, 9:51 PM EDT by
-
The Daily Grind
We manage the basic activities with simple todo lists from Jira. And we have quick, daily chats to see that folks are doing what they hoped to get done and have no blockers, and are coordinating as needed. This is via the Daily Scrum. Typical daily s
Last updated:
Apr 9 2009, 4:00 PM EDT by
-
Collaboration
IM Whatever works... Skype, iChat, ICQ, AIM, ... IRC Create a project room. We use a "bot" that reads the chats and saves it for posterity. It is then made available on the wiki for people to rummage through for various gems that may have existe
Last updated:
Mar 25 2009, 11:04 AM EDT by
-
Tools
"A fool with a tool is still a fool" (tm) <g> But a tool in the hands of an expert are very powerful. And, a tool in the hands of a willing novice who is trying to do better, learn more, can lead that individual to become a craftsman. See: Draw
Last updated:
May 5 2009, 11:15 AM EDT by
-
Tracking hours for every task
From Alan (a thread on agile project management forum): Now as to the why-bother: 1. Government reports require (a) a summary and explanation of R&D activities, and (b) an auditable tally of hours spent doing this. 2. To develop some basis for e
Last updated:
Jan 8 2009, 9:10 AM EST by
-
Drop Iterations, Go Lean
Last updated:
Jan 7 2009, 11:45 AM EST by
-
Using Hours vs Story Points
I use "ideal" hours and a ratio of how many ideal hours there are in a day. See comments near "Story Points" in this page for more details.
Last updated:
Jan 8 2009, 8:49 AM EST by
-
Interrupting an Iteration
Interrupting Development/Emergency Patch I almost never interrupt the current iteration unless something horrible has gone wrong. If there is an emergency "Production Halt" type of "Severity 1" bug, obviously it has to be fixed immediately. He
Last updated:
Jan 7 2009, 11:25 AM EST by
-
Upfront Work
"A lot of upfront work would seem to be contrary to the basic tenet of speed and efficiency of the agile methods." I would vehemently suggest caution when positing this. This is precisely where blind adherence to process falls flat, and using your
Last updated:
Apr 11 2009, 10:26 AM EDT by
-
But What About...
The pages below this one contain an assortment of common questions, counterpoints, curiosity bits...
Last updated:
Jan 7 2009, 11:25 AM EST by
-
Rhythmic Development
One of the first things to recognize about agile, iterative development, is that you have to get the entire team into a sense of rhythm. Take for instance the following figure:
Last updated:
Dec 31 2008, 7:13 PM EST by
-
Issue Management
Initial Issue Creation After the initial up-front activity to get a handle on the basic feature set and Release Planning , we enter the tasks and features into the issue tracker system. From a high-level customer prioritization of the major featu
Last updated:
Dec 9 2009, 9:13 PM EST by
-
Development Process
Consistency is a Quality unto itself Whether it be in process, code, DB design, jira, or the wiki... Being consistent is a tremendous asset to software development! Process Overview In an active software product development projec
Last updated:
Dec 31 2008, 7:07 PM EST by
-
Getting to Production
The Release Decision Process What does it take to get a release to production? Finesse. A Balancing Act There is often a tug of war when it comes to releasing a product to the users. Do we have the right features? We have more id
Last updated:
Dec 31 2008, 9:28 AM EST by
-
Linking Tests to Issues
When you create an issue that is a test for a feature, link the two together via the "Test" link type. The test issue "tests" the related feature issue: The feature that has the test, is "tested by" the test issue:
Last updated:
Dec 30 2008, 11:26 PM EST by
-
Writing Good Issues
I use Jira from Atlassian, so your mileage may vary. But in general, Softwae Development is nothing more complex than accomplishing a list of "to-dos" :-) A feature is: something the product does think marketing brochure bullets or finding it
Last updated:
Apr 30 2010, 10:03 PM EDT by
-
Release Process
What's a Release? We define releases like this: Major Releases, also known as "upgrades," are signified by a change in the first part of the version number, or in the first decimal place of the version number (e.g. version 5.0 to 5.5). These re
Last updated:
Jan 1 2009, 9:36 AM EST by
-
Testing
Last updated:
Dec 30 2008, 10:24 PM EST by
-
Branch Development
As described in Parallel Development , we use branches in SVN to snapshot the code base that reflects the released version of the project. This allows new development to carry on in the TRUNK ; while still allowing maintenance to the released ver
Last updated:
Apr 8 2011, 11:46 AM EDT by
|
|
