Short-term projects are taking priority at many organizations as the trend toward agile IT spreads throughout the enterprise.
TOOLS TRAINING LIVE WEBINARS USER-GENERATED
|Books Events Links White Papers Wikis|
|Language:||All English Arabic French Japanese Korean Portuguese Romanian 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
Agile software development has far and away surpassed agile manufacturing in writing and mindshare. So much so that others in the wider business community have looked at agile software development as a model for other types of working.
Agile planning is organized in different scopes, where each of them are equally important and carry value towards the end goal.
Read about why agility cannot be confined to a process or method...
Consumer brands are increasingly using software companies’ product-development model. Called "agile", this model can cut development time and reduce product failures--but it can be a challenge to master.
Taking Agile's pulse through audits.
This article is about requirements, estimation, and planning in agile software development projects. Agile estimation is often seen as being invaluable, yet others dismiss it as waste. The reasons for this disagreement can be traced to disparities in the Scrum and Lean-Kanban ways of working.
There has been a lot of focus on making annual planning processes more strategic. There is an increased understanding that the portfolio of projects has to be managed against the organization's goals--and that this may require good projects to be stopped. At the same time, organizations are striving to become more adaptable, driving change into projects. Organizations have to be able to respond effectively and efficiently or lose out to their competitors. The growth of agile approaches is part of the solution, but it's not the only answer--and project execution is having to adapt to this new normal. Share your thoughts in our new survey...one lucky participant will win an iPad 2!
Let's examine agile team member roles and behaviors (or "anti-patterns") that are detrimental to the agile process.
We ask people to work differently, to self-organize and share responsibility, but what guidance do we give them on how to do this?