In the second part of this three-part series, I'll cover some common process terms you'll hear working on your first custom software product.
Sizing up a team has many challenges, including managing the flow of standups. Here's a collection of ideas to keep things moving.
For a team to find success, it is important they understand the different types of conflict at play and their opportunities.
Many nuances contribute to a healthy project portfolio for an organization like Atomic Object, and the work of managing that portfolio is never done.
In response to uncertainty, team members may try to eliminate it at all costs. Doing so can consume too many resources and divert attention from real goals.
We often apply metrics to job performance. When it comes to software development, however, this is surprisingly complicated.
Software teams encounter new challenges across people and technology. That means the development of project and team leaders is more critical than ever.
Sometimes, the right choice is to proactively shrink a team to help a client. Time is a valuable resource, and small teams work hard to hit tight deadlines.
With a strong transition plan and a clean exit, you will feel better about the position you’ve left both the project and team in.
When joining an in-progress project, I like to clarify where the project and team are now, check for gaps, and bring an outsider’s perspective.
At first, we used Slack channels primarily for team-based discussion. But then people started making channels devoted to a particular technology or topic.
Lessons from ten years' experience with pair programming.