This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
In Part 1 , I wrote about how “Agile” is not a silver bullet and is not right for every team and every product. This post is about how management fits into agile approaches. Too often, managers think “agile” is for others, specifically teams of people. Managers Create and Refine the Culture.
For far too long, managing risk has been seen as an esoteric business function — designed to control losses and adhere to compliance standards. Leaders who practice what they preach, have conviction, and lead by example are better at managing risks than those that merely pay lip service to ethics, value systems, or codes of conduct.
Every day, I hear more stories of agile coaches or Scrum Masters losing their jobs. Several reasons: No manager cares about “agile” even if they care about agility. So, selling “agile” into the organization doesn’t create any traction for change. You might not like these ideas.
In the agile and lean communities, we talk a lot about transparency. This image is the transparency principle we used in From Chaos to Distributed Agile Teams. I see many organizations succeed better when the less the manager knows, the better the team works. That's because the managers don't explain: Why this product.
For example, at the end of its 2015 fiscal year, Apple’s balancesheet stated tangible assets of $290 billion as a contribution to its annual revenues, with approximately $141 billion worth of intangible assets — a combination of intellectual capital, brand equity, and (investor and consumer) goodwill.
These fears aren’t unfounded: managers across industries have cost targets and technology enables lower-value tasks to move from people to machines. This is true both for “on balancesheet” workers and the gig economy. Everywhere today the news confronts us with deeply held fears of AI and automation.
We organize all of the trending information in your field so you don't have to. Join 55,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content