The world is in a time of rapid change resulting from the usual culprits: The integrated economies and labor market have created a “flat world. The Internet has reduced friction in the marketplace The accessibility of data has revolutionized target marketing The low cost of processing, storage, and software environments (e.g., Java, Python, R) has made application development efficient, enabling innovation and disruptive technology. In the past, building business was associated with stability — creating an organization of lasting value that persisted even through a change of management or some market structure change. Running a business in the face of today’s changes, however, alters the nature of business management. “Agility” is the facility of quick response Read more
Posts Tagged 'agile'
By asking the CEOs of some of the most successful and influential companies in the world, such as GE and Google, a clear definition of innovation management emerges. The definition addresses the need to quickly and effectively implement organizational goals and objectives to remain competitive and the desire to strengthen advantages through the adoption of innovative ideas, products, processes, and business models. Enterprises facing increasing competition and the pressure of technological innovation are beginning to realize that to drive organic business growth and maintain a competitive advantage, they need to discover and implement innovation quickly and with great care to ensure maximum value. One-off innovations are moderately easy to take advantage of, but to create a pipeline of Read more
“Agile” — it’s an intriguing notion. Iterative, progressively elaborated projects with core deliverables to maintain motivation and progress along the way. It makes an extraordinary amount of sense both from a project management and leadership perspective. And up until now, true Agile practice has been refined and confined to a relatively narrow province, guided by trained scrum masters and captured as a distinct (yet, niche) practice within the project management community. 2016 is the year we can all look forward to a host of “new” Agile practices, each with its own nuance, and each with its own subset of practitioners. We’ve been seeing the cracks in the wall for several years, as organizations come up Read more
As we begin another year and try to predict where quality assurance (QA) will go in the next few years, we need to reflect for a moment on where QA has been — especially with the dire predictions in recent years that QA in software engineering is dead. One thing that is dead is the traditional way of doing QA. The days of huge QA departments conducting testing mainly using manual methods, and usually as a phase after the development team is done, are gone. Market pressures and the fast-paced demand of software releases have made sure that relying on only manual testing as your QA strategy is no longer acceptable. Having said this, organizations Read more
Lately, Agilists have been giving the role of middle managers (or possible lack thereof) in Agile transformation a fair amount of attention. While this is a knotty problem, I worry that our polite efforts to re-define the management function might be enabling organizational neuroses and psychoses, instead of helping people address them. Ultimately, we have to use plain language: there are many bad managers out there. Agile exposes their incapacity, and makes delaying the inevitable that much harder. While compiling a complete list of middle management functions might provide some catharsis, this is supposed to be a short blog post. Therefore, I’ll highlight a few that Agile commonly exposes, with the clarity of those photos Read more
The software engineering field has changed a lot over the years. There have been many advances in the field in terms of tools used, how teams build and test software, the speed of delivery, and so on. For teams that have not yet become a true Agile team (every sprint is developed, tested, and production ready), one pattern continues to show itself even though this pattern is a carry over from the days of large waterfall projects. This pattern is the projection and allocation of budget based on the one-third rule. In the days of large waterfall projects, organizations made the assumption that a software budget was allocated one-third per major category: analysis and design, Read more
[All posts in this series: 1, 2, 3, 4] Continuing on the agile framework discussion that Tom and Maurizio have started… Agile frameworks are indeed something that many organizations are now considering. Some of these organizations believe they have been doing agile well at the team level and are now starting to apply agile across their organization. Others are just starting their agile transformations and simply want to do it right the first time. To satisfy the needs of these organizations, numerous agile frameworks are now on the market. Most, if not all, have worked someplace and are the result of someone codifying that experience. But just because it worked in other places, how do Read more