Let's examine agile team member roles and behaviors (or "anti-patterns") that are detrimental to the agile process.
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|
1044 items found
Community Guide of the PMI-ACP|Community Guide of the PMI-ACP Boosting Team Performance Practices|Boosting Team Performance Practices
This wiki has been created to discuss about the transformation organizations into Agile.
We ask people to work differently, to self-organize and share responsibility, but what guidance do we give them on how to do this?
Of course you're great. Why do you need to have an annual review to tell your boss? An Agile Architect talks about an agile approach to the employee review process.
An Agreement is a legal document which is signed between two parties, one party is called the Buyer and another party is called the seller. The Seller supplies the goods and Buyer pays the money in return. An agreement can be a contract, purchase order, understanding or undertaking. It should have legal remedies.
Alignment means that your people and resources are all working toward the same set of goals. In the IT world, we often talk about alignment between business and IT. This means that the business has a clear vision and a set of goals it is trying to achieve. Then everything IT does, supports those goals in the very best way it can. If everything is perfect, which is never the case, then the two are optimally aligned.
Intangible assets, like many produced in the IT world (patents, inventions, a business process or system that offers competitive advantage), contribute to the future revenues. Therefore they can be expensed over time as those revenues occur.
Is it possible to take the core agile (lower-case "a") principle of rapid, focused delivery, and make it applicable to an aim for self-improvement?