Related Content
Can Technology Solve California’s Water Problems? Recent news has shown that California is experiencing a water crisis. In this story, Joe Townsend explores whether or not modern technology, including the building of a desalinization plant, will be able to solve California's water problems. |
||
Four Principles for Designing Your New Agile Project There are guidelines for those transitioning to agile. You have to know how your product releases and how often. Next, you should determine how complex your product is. Johanna Rothman helps you determine what type of product you have and how you can work on it while making the transition to agile. |
||
Performance Review Dos and Don’ts Performance reviews rarely rank high on the list of responsibilities managers enjoy. Giving feedback can be awkward and uncomfortable. Still, some things can make the experience more productive. Read on for advice about preparing for reviews and offering critiques that will be constructive for all. |
||
The Tech Industry's Problem with Ageism Steve Berczuk writes that a hallmark of many tech companies, particularly those practicing agile, is being a flat organization with a company culture based on a meritocracy. When hiring, however, this meritocracy is inconsistent with the importance some companies place on a person's age. |
||
Overcoming Analysis Paralysis Analysis paralysis is that situation when instead of making a decision and getting on with things, you keep overthinking the process and avoiding taking action. It’s often a mental block caused by a fear of doing something wrong, and it's a common workplace affliction. Here's how to deal with it. |
||
How Management Indecision Loses Money and Hurts Your Project Portfolio When managers can’t decide which projects to undertake, they end up making a decision—to not decide. They don’t fund the potentially transformative projects; they go with the safe bets. The difference between when a project goes on the backlog and when it's started eats into your maximum revenue. |
||
Book Review: The Retrospective Handbook Steve Berczuk reviews Patrick Kua's book The Retrospective Handbook: A Guide for Agile Teams. Among the issues Kua addresses are how to lead a retrospective when you are part of the team and how to deal with retrospectives with distributed teams. |
||
Four Reasons to Stick with Daily Scrum Meetings Every team member is required to attend a daily scrum meeting. Pro tip: The ScrumMaster and product owner are team members too, despite their titles of leadership. If you feel you don’t need to attend every daily scrum, then consider these four reasons why you should stick with it. |