If you are thinking of agile as part of a program, each team has to have its own approach to agile. Why? Because each team has its own risks and problems. You don’t need to standardize agile for anyone. If you treat people as if they are adults and explain the principles that you want […]
Today’s job search trap is something we can all identify with: biting off a big chunk of work and not getting it to done fast enough. I suspect we have all been there and done that! How do you avoid this particular trap? I like to assess each of my tasks on my board and
Three Secrets for a Successful Job Search Are you looking for a job? If you are, I bet you’ve received advice from many people–whether or not you wanted it. Here are my three secret ingredients for a successful search: Secret #1: Create a system that works for you. I happen to like personal kanban inside
I recently met someone who thought he could manage his job search with yellow stickies. Given that I recommend personal kanban, I thought we’d be on the same wavelength. Imagine my surprise when he said, “I have stickies all over my computer, to remind me of what I have to do.” Oh no. That’s not
Is the Urgent Consuming You? When you start work in the morning, what do you do? Do you check email, listen to your voicemail? Let the urgent take over your day? Do your meetings drive your day? If you do, you are not alone. Is there a better way? There can be. You can take
Many years ago, I was part of a task force to “standardize” project management at an organization. I suggested we gather some data to see what kinds of projects the client had. They had short projects, where it was clear what they had to do: 1-3 week projects where 2-4 people could run with the
Emergent Projects: Managing the Unpredictable Are you planning a change project, managing your way through a job search, or some other not-totally-deterministic project? Wouldn’t it be nice if life went according to plan? You could create a roadmap first, estimate how long things would take to get done, create a project plan, and do them.
When you’re a project manager for a traditional project, it’s easy to write a project charter. You can sit in your office and write it alone, if necessary. You don’t have to involve the team. On an agile project, is that the right thing to do? Should you even use the same template? Agile projects
What do you do for geographically distributed teams, if you want to move to agile? First question: does the team want to move to agile? Or, does the management want to move to agile? I am serious. I might take the same actions, but for different different reasons. In either case, the team needs to
The point of using agile is to get finish something valuable-to-the-business quickly, to get feedback. Why? For several reasons, but the first one is so you can change the project’s priorities. The second is so you can change the project portfolio. The third is to get feedback on what you’ve done. Okay, you can exchange