Facebook's latest product is a crash course in agile development, and why it's so important to keep it a priority.
More and more stories showing up regarding big companies using agile , although this one is not so much a case history as an aside note at the end. There is an interesting video on facebook's Paper, which is the focus of this piece.
In countries with high power indices, it’s more difficult for people in less powerful positions to talk to people in more powerful positions. A transition to agile exposes this power differential, which can be uncomfortable or intimidating.
Nice observation regarding cultural challenges facing distributed agile trams. Also applicable to multi-cultural centralized teams. Agile always requires education and training.
Agile adoption in organizations where command and control is the most dominant management style can be tricky. There have been situations where an agile transition didn’t deliver the expected improvements, or even failed and was stopped.
Good links to additional articles that grapple with the question of transitioning to agile in a command and control environment. One interesting point in the article - "Management really does need to change, otherwise you didn’t need Agile.."
Are there organizations that are command and control oriented but already practice agile, without knowing it?
Daniel Markham, an agile coach, is asking the question "why there are some "seriously pissed off people about Agile out there? Isn't agile supposed to be warmth, apple pie, motherhood, goodness and all of that?
I missed this article when it came out a month ago, but if the questions raised in this article are the ones every Agile proponent has to answer at some point. This raises most of the ones people will throw at you and therefore will prepare you on what to expect.
The digital revolution has shaken the publishing industry. Six trends, however, highlight new opportunities as well. The explosion in devices, apps, social media"
This slide show, while originally posted in April, provides an interesting look at Internet media usage verses traditional channels such as television. There are also some interesting stats from reports that might not be affordable for a small company, but would be useful in one of your presentations!
The more we learn about the development of Healthcare.gov, the worse the situation looks. The site has been serving myriad errors since it launched, including preventing users from creating...
I've been waiting to read the lessons learned from healthcare.gov. I tell my students - test, test, test. It is an interesting read and no doubt will get more interesting as more of the real story of the project development comes out.
This first article in the series on the Kanban “nine values, three agendas” model, explores the sustainability agenda: a common approach to Kanban adoption at the level of individuals and teams, often motivated by the need for relief from...
If you have been curious about Kanban, then this article series is a good start.
Patterns and Practices for Delivering Software at Scale - a presentation from AgilePalooza Twin Cities: Steve Povilaitis has over 17 years of industry experienc
Great slideshow for introducing and understanding how to use Agile on large projects. Not all slides are intuitive if you have no experience with Agile, but most will get you going in the right direction.
I haven't been to Agile By Example, but be forewarned - this article is focused on software development, not Web project management. There are enough similarities though that you will still probably get some useful ideas by this sustinct recap of various sessions.
When meetings drag on for hours, developers check out.
I'm not sure that the title questions is actually answered in this article. The focus of the article is how to handle planning meetings and addresses a question on what to do when developers complain that the planning meetings are too long. If you face this problem then you will find value in the response.
The fastest moving enterprises all have one thing in common: They don’t let today’s investments in technology slow down tomorrow’s innovations.
Nice slide show and not your usual tips. These seven principles will get you thinking and even make a nice list for those working with sequential projects who are (shhh) borrowing ideas from Agile teams.
Pete Behrens goes over how to keep agile working properly for your organization
Good article on how the transition to Agile involves a need for a cultural change. (doesn't every article mention this?) The point of this article though is that it is best to view the transition as a journey. Best line, "Agile is a process not a destination."