Do you know when your work is done? Are you sure your feature is done? How about your release? Do you know when it’s done? Leyton Collins has some suggestions for you, your team, and your organization on how to know when things are really done.
While many teams can use help structuring their conversations, some teams also need some way to know whether the structured conversations that have taken place have provided sufficient information. Kent McDonald explains how using visualization boards can help in these situations.
Thinking about interacting with the customer at the start of the project? Who would argue against that? Well, it depends on what you call it. It also depends on whether you then do it without the benefit of the rest of the project team. Here, Ulrika Park helps us see what an agile approach to thinking about the requirements might look like.
Kathy Iberle writes that when working on a project, you should take a systems view, which allows you to see the whole development system at once. When you put on your “systems view” glasses, you’ll see that you need to deal with the whole system, not just a single team’s part of it.
Kent McDonald introduces us to Arthur, a middle manager and product owner in a medium-sized insurance company who has been assigned to take on an agile project. For those unfamiliar with agile, the terminology and techniques of agile approaches can seem strange and often a little silly when not accompanied with an explanation as to why those techniques exist. Kent explains the challenges product owners like Arthur face and how to make product owners understand agile better.
Managing requires a different skill set from technical work, yet many companies promote their best technical workers to management positions. Here are some things to consider when it's time to promote your technical workers.
If you have a cheerleading manager (or, worse, if you are a cheerleading manager) in a troubled organization, then your team is likely missing its purpose. Replace those cheers with transparency, and you might be surprised by the solutions your team will come up with.
Increasing the amount of time someone spends on work does not directly result in better work. In fact, depending on the person, the opposite may be the case—spending less time at the office may improve the results. Johanna tackles myths of measuring work by time.
Your clients may not understand why you follow certain practices as a project professional. They may encourage you to take shortcuts that they believe will save time, money, and difficulty. You know better, but how can you convince them?