On June 1st, Dr. Ivar Jacobson delivered a keynote address at the annual International Conference on Software Engineering. Ivar shared his views on the history of software engineering to date and where we need to go from here.
In this blog article, the authors share the first game that can be played using the Scrum Essential Cards. Use Practice Patience as a great way to perform a holistic retrospective on your Scrum adoption.
IJI has recently had the pleasure of working with Jeff Sutherland on a set of Essence cards that faithfully represent the Scrum Guide. As well as acting as a handy physical, and online glossary, the cards can be used to play games and help us all get better Scrum.
In this new blog series, Brian Kerr and Ian Spence present a selection of the games you can play using the Scrum practice cards and, in some cases, other cards from Essence itself or from other complementary practices.
On 20 April, 2018, Dr. Ivar Jacobson will instruct a public lecture at Chalmers University. During his talk, he will revisit the history of methods, explain why we need to break out of our repetitive dysfunctional behavior, and introduce Essence: a new way of thinking that promises many things, one of them being to dramatically change the way we educate in software development to increase the competency in our profession.
The way we develop software struggles to keep pace with changes in technology and business. Even with the rise of agile we still see people flip-flopping from one branded method (or to be more fashionable framework) to another throwing away the good with the bad, and behaving more like religious cultists than scientists.
Dr. Ivar Jacobson delivered this presentation at a keynote address at SECR Russia in October 2017. He revisited the history of methods, explained why we need to break out of our repetitive dysfunctional behavior, and introduced Essence: a new way of thinking that promises to liberate the practices and enable true learning organizations.
Scrum Inc., the world’s premier Scrum training and consulting provider, today announced that it has been working with its partner Ivar Jacobson International (IJI), a leading consulting, coaching and training company for enterprise-scale agile software development, to apply Essence to build a navigable glossary of the essential elements of Scrum. This glossary will be used at Scrum Inc. and in Certified Scrum training courses, hosted by IJI and taught by Jeff Sutherland in the United Kingdom in February 2018.
Software Engineering Conference in Russia (SECR) is one of the brightest annual IT events in the country. The 13th edition of the SECR will take place on October, 20-22 in Saint-Petersburg and the conference program will include a key-note address by IJI Chairman Dr. Ivar Jacobson.
The Industrial Internet Consortium predicts the IoT (Internet of Things) will become the third technological revolution after the Industrial Revolution and the Internet Revolution. Its impact across all industries and businesses can hardly be imagined. Existing software (business, telecom, aerospace, defense, etc.) is expected to be modified or redesigned, and a huge amount of new software, solving new problems, will have to be developed. As a consequence, the software industry should welcome new and better methods.
This article makes the case that to be a major player in this space you will need a multitude of methods, not just a single one. Existing popular approaches such as Scrum and SAFe (Scaled Agile Framework) may be part of the future, but you will also need many new methods and practices—some of which aren’t even known today. Extending a single method to incorporate all that is needed would result in something that is way too big and unwieldy. Instead, the new OMG (Object Management Group) standard Essence can be used to describe modular practices that can be composed together to form a multitude of methods, not only to provide for all of today’s needs, but also to be prepared for whatever the future may bring.
To be agile as teams, we need to adjust our approach to meet our immediate challenges and needs. To be agile as an organization, we need to learn collectively and evolve our approach over time to support our evolving mission, so that we continue to excel in an ever-changing environment.
We would not call a TV set “adaptive” if, in order to adjust the volume, we had to throw it away and replace it with a model with a different volume setting. So why are we prepared to accept process frameworks that leave us in a similar predicament every time we want to improve our product development performance as an organization?
