Marcus Blankenship and I wrote a follow-up piece to our first article, mentioned in Discovery Projects Work for Agile Contracts. That article was about when your client wants the benefit of agile, but wants you to estimate everything in advance and commit to a fixed price/fixed scope (and possibly fixed date) project. Fixing all of […]
Linda Rising gave a great talk last night at Agile New England. Her topic was problem-solving and decision-making. One of her points was to discuss the problem, out loud. When you talk, you engage a different part of your brain than when you think. For us extroverts, who speak in order to think, this might
People often ask me, “When is agile right or not right for a project?” I’ve said before that if the team wants to go agile, that’s great. If the team doesn’t, don’t use agile. That answer is insufficient. In addition to the team, we need management to not create a bad environment for agile. You
Marcus Blankenship and I wrote an article, Stay Agile with Discovery, to discuss how to help your clients see the benefits of working in an agile or more agile way. We have seen too many clients want “agile” and not want all the responsibilities that being a Product Owner or customer involves. If your client asks
In a recent workshop, a participant asked me, “What does agile mean? How do you know if you are agile?” He wants to use kanban to see the flow of work through his group. Someone told him he needed to use iterations to be agile. (I had a little rant about this in What Does Agile Mean
If you’re the project manager for a geographically distributed team, you have likely encountered time zone challenges in running your meetings: 7 a.m. New York time is 8 p.m. in Singapore. Meetings at these times can exhaust everyone. Here’s a common scenario faced by managers of distributed teams: “We’ll have our next standup tomorrow, same
In Part 1, I discussed the agile project system. In Part 2, I discussed the tester’s job in agile. In Part 3, I discussed expectations about documentation (which is what the original question was on Twitter). In this part, I’ll talk about how you “measure” testers. I see a ton of strange measurement when it
In Part 1, I discussed how an agile approach changes testing. In Part 2, I discussed how the testers’ job changes. In this part, I’ll talk about expectations. Since the developers and testers partner in agile, the testers describe their approach to testing as they work with developers on the code. (This is the same
Last week, I attempted to have a Twitter conversation about agile and testing. I became frustrated because I need more than 140 characters to explain. This is my general agile picture. For those of you can’t see what I’m thinking, the idea is that a responsible person (often called a Product Owner) gathers the requirements
In Part 1, I discussed the project system of agile. In this part, I’ll discuss the need for testing documentation. In a waterfall or phase-gate life cycle, we needed documentation because we might have had test developers and test executors. In addition, we might have had a long time separating the planning from the testing.