All of us have seen highs and lows of Agile teams while working in different organizations. The interesting fact is that each organization has its own version of Scrum methodology that is widely believed to be the savior of sluggish development and productive measurement.
TOOLS TRAINING LIVE WEBINARS USER-GENERATED
|Books Events Links White Papers Wikis|
|Language:||All English Arabic French Japanese Korean Portuguese Russian Spanish|
|Access:||All Free Premium|
|All A B C D E F G H I J K L M N O P Q R S T U V W X Y Z|
29 items found
ProjectManagement.com is excited to launch its "Scrum Success" survey! This survey is intended to uncover how you are using Scrum in your organizations and project management efforts. If you work on software projects or even non-software projects, we would like to have your input on whether you use Scum or not. Please take a few moments to complete our survey and share your experiences. One participant will be randomly selected to win a $500 gift card!
The Financial Times (FT) has formed a group of in-house developers to focus on a high volume of fast projects in order to increase its agility.
Every organization faces patches of rough weather in its journey toward success. How these experiences are managed sets apart an awesome organization from "just another" one. Here's a case for adopting Scrum to tackle some of the most common yet tricky problems.
Most of us working in agile development or agile management are neither airline pilots nor surgeons, but we deal with complex projects involving many people and teams--and lots of rapidly changing details where evil lurks. Simple, customizable checklists are highly effective in slaying the complexity devil.
It's not only the IT industry that lives in "beta." Increasingly, the construction industry is using agile techniques to deliver projects on time and on budget.
As companies transition to Agile and Scrum to manage their software development projects, how does this affect the work of business analysts?
The project management landscape is changing. As our projects are becoming more challenging, it is impossible to determine the status or health of a project from just time and cost alone. Yet this is what we tried to do for more than five decades. Now we are beginning to recognize the need for additional metrics and KPIs.
"Scrum is easy; implementation is hard." You've probably already heard that many times. The same goes for some particular tools, like planning poker. The practice itself is very straightforward, but how to use it productively over a long period of time is harder. In this article, the author shares a simple, lightweight technique that makes the sizing process a little easier in the daily life of a Scrum team.
The product backlog is an important tool: It lists ideas, requirements, and new insights. But is it always the right tool to use?