Posts

White paper ideas on Iterations

This is a good white paper regarding developing in iterations on Agile teams. As you will notice, it does not mention Use Cases or requirements documents. You could assume the requirements are reviewed in the iteration planning meetings or in a previous meeting. In that case, you would use the iteration planning meeting to ask questions, review the requirements and estimate the work for the iteration. http://tig.cmptechnetwork.com/cgi-bin4/DM/y/nBNCe0Nsnos0YLp0GyYS0ED

Article on Dev and Testing schedules during an iteration

This is a good article addressing developing features and QA testing them during the same iteration. Chris offers a good example process. I like the comments that followed because you see different points of views regarding the topic. This brings to light some of the issues with Dev and QA cohesion. I think the example Chris provides makes sense but I also sympathise with the QA person explaining the issues of retesting changing features. IMHO, I think QA has to catch up with development in "agile" thinking. Developers know code is going to change and it will change a lot. With CI, Unit Testing and refactoring, the features evolve over time. QA needs to follow the same pattern in Agile environments. They are not retesting features, they are testing. Features are not half complete, they are not done. (Done means a feature is developed, tested, and accepted) QA should work closer with developers and should us continuous testing (CT) throughout the iteration. T...

Why is success measured by estimates?

http://blog.cutter.com/2008/11/04/software-estimation-a-tough-beast-to-control/ This article was posted under a quoted title "“a tough beast to control”. I agree with the title but 100% disagree with the survey. Meeting estimates IS all about "control." If you want to meet an estimate you have to give the customer exactly what you agreed and control (Deny) any changes they want. Here is an analogy which is similar to one Robert Martin used. You go to your doctor and they say you have a tumor in your liver.(arbitrary organ). They schedule the surgery and open you up. While removing the tumor they find another one in your pancreas .(arbitrary organ). Using estimates as a measure of success would encourage the doctor to sow you back up, let you heal and then say, we did not estimate the pancreas tumor so we could not remove it because we would exceeded our estimate by 10%. Also, I will not get my bonus if we do that and you might not pay for it. The doctor is more ...

Comparing Waterfall and Agile Change

Chris provides a great real world example of how our methods of embracing change correlates to software development. This is one of the best posts I have seen on understanding changes in software development. I see my self using this analogy in the future. Hopefully he does not mind. :) When you use this analogy on your customers, be ready for the follow up question. "So how do we do GPS development?" The customer will need to see your confidence and understanding of Agile development before they buy into it. http://feeds.feedburner.com/~r/ChrisSpagnuolosGeoscrum/~3/428653167/

Technical Managers

Here is an excellent post from Managing Software Development . The article does not distinguish between managing and leading but that is OK because the indirect point is you need to be good at both. I wonder if the amount of time he had to manage the team impacted his management style while the PM was out on vacation. If he had more time, would he had done more. Does this mean people manage to the amount of time they have available? More than likely, Yes. Does this mean that some PMs or technical managers have too much time? No. I think their time is just used in wrong activities. When leading a development team you have to look at each role and make sure they are focusing on the core duties of the role and remove obstacles from their paths. If your PM can't tell you your budget and forecast at any moment in the project, they are probably doing other things that are not as important. http://www.noop.nl/2008/05/how-to-select-a-fine-technical-manager.html?cid=135566419#commen...

Barry Boehm, "Defects found early in the development cycle are less expensive" does not apply today.

I heard this in a podcast and tracked down the session notes where it was said. “why it had taken so long for the agile development methodologies to become known and accepted.” Here were the responses from the panel: T om DeMarco responded quickly with the quip, “It’s all Barry ’s fault!” He went on to suggest that we had all been brainwashed by Barry Boehm ’s argument, first published in his Software Engineering Economics book, that the cost of repairing defects rises exponentially the later they’re found in the software life cycle (for a more recent exposition of this point, see the December 19, 2005 Dr. Dobb’s article by Yochi Slonim , “ The Software Quality Lifecycle “). He said that as a result, the commandment “get the requirements right!” was drummed into the heads of a generation of software engineers. Tom turned towards Barry , smiled, wagged his finger, and said, “And I have never forgiven you!” Barry Boehm relieved the tension in the air by agreeing with Tom . He explained t...

Branching Should be a Planned Activity

Most teams do not consider branch code until it is too late. Many projects forget about branching because they never plan or plan for branching code. If you delivery process is unstable, it is impossible to plan your branching. At times this will cost your customers money in source control merging, developer down time, defects and setting up complicated branches. Branching code should be discussed during iteration planning and be an estimated task or story to be completed at the end of an iteration before releasing or as a release activity. Keep in mind the impact of the next iteration’s or release’s development. This is a good article about Branching Strategies. http://labs.seapine.com/wiki/index.php/Surround_SCM_Branching_Strategies#Branch_By_Purpose