Related Content
 |
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. |
|
 |
What If You Don’t Want to Be a Manager? Management isn't for everyone, but many technical professionals worry that they’ll reach a dead end in terms of compensation and organizational clout if they don’t move into management. Read on to learn how to gracefully turn down an offer and how to excel in your career while remaining a techie. |
|
 |
Using Root Cause Analysis When Your Project Fails Venkatesh Krishnamurthy explains how root cause analysis (RCA) can be used to help your team members avoid personal conflicts and resentment when a project fails. Conducting an RCA session can help to divert attention from people to process improvement. |
|
 |
Why Being Kind Will Make You a Better Leader When you think about successful leaders, kindness is usually not among their first qualities. But kindness and compassion shouldn’t be equated with weakness. In fact, in organizations led by compassionate bosses, employees tend to be more loyal and dedicated. Here's why you should aim for kindness. |
|
 |
Why Both Agile and Math Can Be Difficult to Learn Agile software development can be hard, but many of the challenges may be more about perception than actual constraints. Many teams find an agile environment to be both more productive and more pleasant. This sounds similar to current research studying people's math ability. |
|
 |
Seven Steps for Starting Scrum Project taking a long time to get out of the analysis phase? Is there ambiguity and a lack of transparency in all moving parts? Is your project on its way to becoming a money pit? If you answered yes to any of these questions, it might be time to start using Scrum to save your project. Read on. |
|
 |
Four Steps to Avoid Micromanaging and Get Good Work Results There is a big difference between micromanaging people and understanding their state. If you need a project done quickly, you may be tempted to stand over employees' shoulders asking, "Is it done yet?" But if you leave the team alone and simply check in regularly, you'll get better results. |
