Implementing Scrum in a standalone organisation (such as a product company) derives directly from the framework. Yet some aspects are open to interpretation for Scrum teams in an agency providing software development services to clients. Both The Scrum Guide and most literature on best practices of implementing Scrum lack the notion that the so-called “organisation” may be, in fact, two separate legal and business entities: the agency and the client. How do you apply The Agile Manifesto’s “Customer collaboration over contract negotiation” when the underlying “organisation” exists precisely because of a contract?
Once upon a time, Alice is walking down the corridors of a building, with a bag full of assorted items, and passes by Bob, who is standing close to a wall, barefoot. But who is Bob, you might ask?
I see: you are uneasy about interrupting someone, and you feel you might as well do it gently. Break the ice, prepare the turf, something like that. You are asking that guy a favor, a question, and you don’t want to overwhelm him right off the bat. Except you might be doing something worse: interrupting that person to notify him that you’re still typing whatever it is you want to send his way.
Slack has announced a new feature called Threads, aimed at taking the clutter out of public channels. At first, you might think that Direct Messages already covered that, but it’s not so.
Some say it’s so easy and versatile that there’s no wrong way of using Trello. From my experience using it in agile software development, I beg to differ: there is.