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.
In this roundup of interesting software news for April, read about how developers are more satisfied with their jobs than ever before, and a fascinating new survey to be conducted on agile software development practices in the New York metropolitan community.
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.
The importance and usage of regression testing have grown in the past decade with the increased adoption of agile development methodologies. Rajini Padmanaban looks at the value of regression testing, how it has become a target for test automation, and how it fits into the agile world.
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.
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.
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.
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.
An open environment is needed to succeed in an agile implementation. Many organizations favor a change in office layout to promote collaboration and team interaction. However, employees may not always be on board with the decision. Consider these points before making the switch at your workplace.
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.