Making cultural change in an organisation is hard, and fraught with risk. Adopting Agile principles is a major cultural shift for many organisations. Management consultant and author Steve Denning has been researching what makes change stick, and provides some concrete advice for change agents.
The 2010 US Scrum Gathering kicked off Monday in Orlando with a buzzworthy day of "deep dive" learning, collaboration, and healthy debate.
Jean Tabaka spoke at the Agile Australia 2009 conference in Sydney on 15+16 October. Her keynote talk titled "12 Agile Adoption Failure Modes", in which she identified a dozen common roadblocks that can prevent effective transformation to Agile techniques in organizations.
52% of the .NET developers surveyed by Typemock think that unit testing can help companies avoid law suits associated with the proposed EU software liability bill. What does this say?
The state of the art in political technology evolved radically 2004-2008. In 2004, software development in Democratic political campaigns consisted of a few rag-tag hackers taking shots in the dark and building applications. In 2008, political start-ups built innovative social applications that raised nearly 1/2 billion dollars, and elected a President.
The daily scrum is an important meeting within the Agile team. According to Scrum, only the pigs are allowed to speak during such meetings and chickens should just listen. Is there a limit on the maximum number of chickens, who could attend the daily scrums?
At the Software Education SDC conference in Melbourne, Australia, and Wellington, New Zealand, last week, Ivar Jacobson, author of the original work on Use Cases, the Unified Modeling Language and the Rational Unified Process, said that Agile development needs to “Get Smart”.
Jeff Patton explains why thinking of agile as culture and not just process explains resistance and difficulty in teaching and learning the approach. Furthermore he suggests that culture generates process, and therefore we should focus on culture first before process and techniques
Recently there has been an active discussion in the Scrum Development Yahoo Group about handling an "under-performing" team member. In the 130+ response thread, "Rotten apple in Scrum team", talk ranged from advice for the primary question, to talk of team morale and who manages it, to the classic debate of measuring individuals, to distinguishing whether a team is really a "team", and more.
What are the tricks to successfully transitioning from cubicles to a team room? What are the concerns? Ideas include: make the change an experiment, make sure everyone is heard.
IT has consistently failed to deliver expected value time and time again. According to Ian Thomas, Industrialization (componentization, specialization) may be a solution for supporting software agility and reliability in the new business environment.
Struggling with Agile Adoption? Amr Elssamadisy ran a session on what makes adopting Agile processes difficult. He provided the audience with three models for understanding the problems seen during adoption.
A Scrum team has no designated leader; the team is expected to self-organize. Similarly, one of the world's most renowned orchestras has dispensed entirely with the role of conductor in favor of a process where leadership is shared and decisions are made by the team. Along the way, they have learned lessons and ways of working together that any Scrum team can benefit from.
As organizations continue to grow their IT investments (bought, borrowed, or built) and concepts like Business Process Management and Service Oriented Architecture become more common, the role of Enterprise Architecture (EA) has become more common. Recently, several people in the EA community have spoken about its current state.
No software project is perfect, nor is the organization in which the project takes place. When your software project goes wrong, do your team members complain, or do they take corrective action? The Complaint Free World project encourages people to take notice of how often they complain, and reduce the frequency of the complaints, aiming for a goal of twenty-one complaint-free days.