Related Content
 |
Managing Risk in an Agile Project Scrum does not have any specific risk management practices as compared to the PMBOK. However, everything you do in Scrum—as well as any other agile method—will help you identify risk at an early stage. Venkatesh Krishnamurthy explains how to manage risks in agile projects. |
|
 |
Project Management Is Not a Dirty Word Some people dislike the idea of agile project managers, but for teams transitioning to agile, there is a place for management. That place is creating an environment in which the team learns how to self manage. Read on to discover how a PM should offer support and servant leadership to an agile team. |
|
 |
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. |
|
 |
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. |
|
 |
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. |
|
 |
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. |
