At the OOP 2015 conference Colin Hood talked about bridging the gap between requirements engineering process definition and successful iterative roll-out. He presented how the introduction of improvements to requirements engineering can be done better when done step by step, and how relative safety is needed to enable people to take the steps.
CA Technologies recently published a study on the perceptions of 1,425 IT and line of business (LOB) executives on DevOps. It found that 88% of respondents have adopted (24%) or are considering adopting (64%) DevOps. The study focuses on the views of executives (e.g.: C-level, VPs, Directors) at organizations with revenues of at least $500M, bringing a different perspective on the subject.
Kanban talks about limiting work in progress (WIP) as a way to manage workflow. “Limiting WIP is hard enough, but selling it can be nearly impossible” said Jim Benson. At the Lean Kanban Central Europe 2014 Conference he talked about how to convince others to limit WIP.
Successful adoption of agile is related to the approach that is used to introduce changes in the organization. Organization can do a top down “mandated” implementation or use a different approach. Kanban can be used as a way to kick start agile, allowing teams to opt-in to agile practices when they feel ready for it to create a sustainable new way of working .
A case study on creating buy-in and commitment for flow thinking using a mental model and metaphor was presented at the Lean Kanban Central Europe conference. InfoQ interviewed Håkan Forss and Erik Schön about their journey from methods & tools to principles & mindset and how they use visual management to implement flow thinking and improve the product development flow at Ericsson.
As technologists we often never question how technology is affecting us and our world. This interview with Eric Brende presents an a different view on progress, innovation and technology.
Tony Wong, a project management blackbelt, enumerates some practical points on individual procutivity. This article wonders how well these apply to software development and contrasts his list with that of other lists.
Software development is known to be a creative process. The failure of traditional methods, where the dynamic environment of software development was ignored, made Agile methods fairly popular. There has been a growing adoption of Agile methodologies, particularly Scrum. However, is everything all right with Agile? Kai Gilb does not think so. He suggested that there are serious flaws with Agile.
The fourth annual 'State of Agile' survey is open for public participation. The 6-page survey takes 5 to 10 minutes to complete and participants remain anonymous. Over the past 3 years the survey, sponsored by VersionOne, has gauged how widely agile practices have been adopted, as well as the results obtained.
An executives job is not over once they've justified agile to their teams and paid for training. To make a transition successful, its required this executive provide sustained support. Esther Derby takes a moment to describe what she believes to be the 3 most important aspects of this ongoing support.
Sebastian Hermida has put together a free online tool to help teams get a better understanding of how well they're doing adopting agility. The site, abetterteam.org, is based on the "Assess Your Agility" quiz Jim Shore and Shane Warden include in their book, The Art Of Agile Development.
James Shore has declared agile to be in decline. He cites the many teams doing 'sprints' and stand-up meetings, without adopting any of the technical practices necessary to produce high-quality software over the long-haul. In his estimation, this has led to thousands of Scrum teams doing agile so poorly that they will almost certainly fail, and possibly take the agile movement with them.
The results of Version One's 3rd annual 'State of Agile' survey are in. According to the survey, agile practices are being used more widely and with impressive results. More than half of the respondents indicated that 90 - 100% of their organization's agile projects have been successful, and 93% indicated that agile practices had enhanced their ability to respond to changing priorities.
While SOA was the big name in the buzzword tag cloud, BPM is quickly getting bigger and bigger. As organizations are becoming more aware of the need to tame their processes in order to get the benefits of IT investments, BPM is gaining importance and mindshare inside and outside of IT. Is one more important for your architecture?
Greg Smith offers an in-depth practical perspective on making your agile transition just as much about culture change as it is about process change.