Welcome!

Microservices Expo Authors: Flint Brenton, Elizabeth White, Pat Romanski, Cameron Van Orman, Jason Bloomberg

Related Topics: Microservices Expo, Java IoT, Microsoft Cloud, Machine Learning

Microservices Expo: Blog Feed Post

A Brief History of the Agile Movement

Are you aware of how the agile movement happened?

1992 – Crystal Methods

Crystal was the starting point of the evolution of software development methodologies which ultimately resulted in what we know as agile movement. The honor of creating Crystal goes to Alistair Cockburn. The methodology was named “Crystal” only in 1997.

Crystal can be applied to teams of up to 6 or 8 co-located developers working on systems that are not life-critical. You can see the seeds of agile manifesto in Crystal because it focuses on – (1) Frequent delivery of usable code to users, (2) Reflective improvement and (3) Osmotic communication preferably by being co-located.

Here is a post by him on “Notes on the writing of the agile manifesto“.

He is a consulting fellow at Humans and Technology which he had founded. (See: His Biography page)

I could not locate him in LinkedIn.

1993 – Refactoring

Refactoring was coined by Bill Opdyke in a paper titled “Creating Abstract Superclasses by Refactoring”.This is how Wikipedia describes code refactoring:

Code refactoring is “disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior”, undertaken in order to improve some of the nonfunctional attributes of the software.

He is now the Architecture Lead at JPMorgan Chase. (Soure: LinkedIn profile)

1994 – Dynamic Systems Development Method

DSDM, unlike all the other items listed in this post, was created by a Consortium. The consortium was an association of vendors and experts in the field of software engineering. The objective was to “jointly developing and promoting an independent RAD framework” by combining their best practice experiences.

There isn’t any individual who can be credited with the creation of DSDM but Jennifer Stapleton, as one of the founder member of DSDM consortium was instrumental in the initial compilation of thoughts.

She is now a management consultant in UK. (See: LinkedIn profile)

Arie van Bennekum, one of the authors of the agile manifesto has been actively involved in DSDM and the DSDM Consortium since 1997.

DSDM focuses on the following 8 principles of (1) Focus on the business need, (2) Deliver on time, (3) Collaborate, (4) Never compromise quality, (5) Build incrementally from firm foundations, (6) Develop iteratively, (7) Communicate continuously and clearly and (9) Demonstrate control. Again, you can see the seeds of agile manifesto!

He is now a Senior Consultant, Programmanager, Project Manager, Facilitator, Trainer,  Coach, Mentor, Teacher etc. in Netherlands. (See: LinkedIn profile)

1995 – Scrum and Pair Development

Scrum

SCRUM was jointly created by Jeff Sutherland and Ken Schwaberwho presented a paper describing it at OOPSLA ’95 in Austin, Texas.

Jeff Sutherland is the CEO at Scrum, Inc. (Source: LinkedIn profile).

Ken Schwaber is a founder of Scrum.org. (Source: LinkedIn profile).

Mike Beedle has been one of the very early adopter on Scrum and has introduced Scrum to many organizations since the mid-90′s.

As you know Scrum has practically been the de facto standard for agile.

He is now the Founder and CEO at Enterprise Scrum. (See: LinkedIn profile)

Pair Development

Pair Development as a concept was simultaneously but independently written about by more than one person.

Jim Coplien published a paper titled “A Development Process Generative Pattern Language” which contained a pattern “Developing in Pairs”.

He is a Lean and Agile Software Development Coach in Denmark. (Source: LinkedIn profile)

Larry Constantine talked about “Dynamic Duos” in his book “Constantine on Peopleware” published in the same year. This concept went on to become an integral part of Extreme Programming.

Though lot of research has been conducted to show the effectiveness of pair programming, the concept or philosophy does not really reflect in the Agile Manifesto.

He is now a Novelist, and University Professor in USA, (Source: LinkedIn profile)

1997 – Feature Driven Development

Feature Driver Development was initially devised by Jeff De Luca.

The best practices of FDD are, (1) Domain Object Modeling, (2) Developing by Feature, (3) Individual Class (Code) Ownership, (4) Feature Teams, (5) Inspections, (6) Configuration Management, (7) Regular Builds and (8) Visibility of progress and results.

Interestingly, “Individual Class (Code) Ownership” goes against the concept joint code ownership which is considered a key practice today.

He is now the President at Nebulon. (Source: LinkedIn profile)

However, the FDD process was explained to the world through the publication of the book “Java Modeling in Color with UML: Enterprise Components and Process” which he coauthored with Peter Coad.

He had built and sold TogetherSoft to Borland. Currently he is into many things other than Agile! (See: petercoad.com)

He has a LinkedIn page but it is empty with no connection!

Jon Kern, one of the authors of the agile manifesto, had closely worked with both Jeff De Luca and Peter Coad and had helped shape the charter on FDD.

Here are his “Agile Manifesto Notes – Feb 2001, Snowbird, Utah“. These have been dug out and hosted by Jeff Sutherland.

He describer himself as Software Development Quarterback and is associated with multiple companies. (See: LinkedIn profile)

1999 – Many Things Happened

Adaptive Software Development

Jim Highsmith formalized the Concept of Adaptive System Development and published a book with the same name.

The idea grew out of his work on Rapid Application Development methodologies.He proposed a three phase lifecycle of – (1) Speculation, (2) Collaboration and (3) Learning.

He has also written the history or the story behind the formulation of agile manifesto.He is now an Executive Consultant at ThoughtWorks. (See: LinkedIn profile)

The Pragmatic Programmer

Andrew Hunt published the book The Pragmatic Programmer: From Journeyman to Master.

The book laid out characteristics of a pragmatic programmer as the one who is (1) Early adopter / fast adapter, (2) Inquisitive, (3) Critical thinker, (4) Realistic and (5) Jack-of-all-trades.

He describes himself as Pragmatic /\ndy — speaker, author, publisher! (See: LinkedIn profile)

The coauthor of the book was Dave Thomas.If you go through the detailed list of recommendation you will see its influence on the manifesto.

Here are his recollection of the what transpired in the meet in 2001 February – “Some Agile History“.

He describes himself as a Software Visionary! (See: LinkedIn profile)

Extreme Programming, User Stories, Release Planning and Continuous Integration

While Kent Beck was working at Chrysler he developed the concept of Extreme Programming. He published the method in 1999 as a book – Extreme Programming Explained.As a part of Extreme Programming, he also introduced the concept of User Stories and Release Planning.

The methodology specifies best practices for planning, managing, designing, coding and testing.

He is at Facebook and calls himself a Programmer!! (See: LinkedIn profile)

Apart from being a collaborator for the in XP, Ward Cunninghamis also as the creator of the Wiki.

Apart from being the Founder of Cunningham & Cunningham, he is also the CTO at CitizenGlobal. (See: LinkedIn profile)

Ron Jeffrieswas also the collaborator and three of them together are considered as the founder of XP.

His biography page states that he developing software longer than most people have been alive. (See: Biographical Notes).

I could not locate him in LinkedIn.

Though some people think that Martin Fowler introduced the term Continuous Integration in reality CI has also been coinedby Kent Beck.

Here is his recollection on the “Writing The Agile Manifesto“.

He calls himself an author and speaker and is working with Thoughtworks. (See: About Martin Fowler)

I could not locate him in LinkedIn.

2000 – Events leading up to the Manifesto

Bob Martintook the initiative to get the ball rolling on organizing the historic meeting to be held on February 2001 at “The Lodge” at Snowbird ski resort in the Wasatch Mountains of Utah.

He is the Owner of Uncle Bob Consulting. (See: LinkedIn profile)

2001 – Agile Manifesto

2001 February + ‘The Lodge’ at Snowbird Ski Resort + 17 Thinkers = Agile Manifesto

Kent Beck, Mike Beedle, Arie van BennekumAlistair CockburnWard CunninghamMartin Fowler, James GrenningJim HighsmithAndrew HuntRon Jeffries, Jon KernBrian Marick, Bob MartinStephen MellorKen SchwaberJeff Sutherland, and Dave Thomas

2002 – More Agile Concepts

Test Driven Development

For TDD the credit goes to Kent Beck. The concept of Test Driven Development also originated from XP test-first approach. It was given a shape later by Kent Beck through the book Test Driven Development: By Example.

Planning Poker

The concept of Planning Poker was formulated by James Grenning.

Here is the original paper.

He is the Founder of Renaissance Software Consulting. (Source: LinkedIn Profile)

What about Brian Marick and Stephen Mellor?

He is the Owner at Exampler Consulting and calls himself Software consultant, specializing in agile methods with a testing slant. (See: LinkedIn profile)
He calls himself a “Freeter”, a Japanese word, derived from English, that means “free agent.” (Source: His home page)He resides in Zimbabwe and here is his LinkedIn profile.

2003 – Lean Software Development

Is Lean Software Developmentan extension to agile methodology? Should we look at it as something distinct from agile? Should it find a place in this post? I have included it for the primary reason that many agilists consider it to be one of the future directions of agile movement.Anyway; term was coined by Mary Poppendieck and Tom Poppendieckin 2003.

It is an adaptation of lean manufacturing principles and practices to the software development. There are seven principles – (1) Eliminate waste, (2) Amplify learning, (3) Decide as late as possible, (4) Deliver as fast as possible, (5) Empower the team, (6) Build integrity in and (7) See the whole. Amplify learning, deliver as fast as possible, empower the team etc. goes very well with agile principles.

I am not so sure about eliminate waste and see the whole.

Read the original blog entry...

More Stories By Udayan Banerjee

Udayan Banerjee is CTO at NIIT Technologies Ltd, an IT industry veteran with more than 30 years' experience. He blogs at http://setandbma.wordpress.com.
The blog focuses on emerging technologies like cloud computing, mobile computing, social media aka web 2.0 etc. It also contains stuff about agile methodology and trends in architecture. It is a world view seen through the lens of a software service provider based out of Bangalore and serving clients across the world. The focus is mostly on...

  • Keep the hype out and project a realistic picture
  • Uncover trends not very apparent
  • Draw conclusion from real life experience
  • Point out fallacy & discrepancy when I see them
  • Talk about trends which I find interesting
Google

@MicroservicesExpo Stories
The nature of the technology business is forward-thinking. It focuses on the future and what’s coming next. Innovations and creativity in our world of software development strive to improve the status quo and increase customer satisfaction through speed and increased connectivity. Yet, while it's exciting to see enterprises embrace new ways of thinking and advance their processes with cutting edge technology, it rarely happens rapidly or even simultaneously across all industries.
Is advanced scheduling in Kubernetes achievable? Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, will answer these questions and demonstrate techniques for implementing advanced scheduling. For example, using spot instances ...
With the rise of DevOps, containers are at the brink of becoming a pervasive technology in Enterprise IT to accelerate application delivery for the business. When it comes to adopting containers in the enterprise, security is the highest adoption barrier. Is your organization ready to address the security risks with containers for your DevOps environment? In his session at @DevOpsSummit at 21st Cloud Expo, Chris Van Tuin, Chief Technologist, NA West at Red Hat, will discuss: The top security r...
DevSecOps – a trend around transformation in process, people and technology – is about breaking down silos and waste along the software development lifecycle and using agile methodologies, automation and insights to help get apps to market faster. This leads to higher quality apps, greater trust in organizations, less organizational friction, and ultimately a five-star customer experience. These apps are the new competitive currency in this digital economy and they’re powered by data. Without ...
With the modern notion of digital transformation, enterprises are chipping away at the fundamental organizational and operational structures that have been with us since the nineteenth century or earlier. One remarkable casualty: the business process. Business processes have become so ingrained in how we envision large organizations operating and the roles people play within them that relegating them to the scrap heap is almost unimaginable, and unquestionably transformative. In the Digital ...
These days, APIs have become an integral part of the digital transformation journey for all enterprises. Every digital innovation story is connected to APIs . But have you ever pondered over to know what are the source of these APIs? Let me explain - APIs sources can be varied, internal or external, solving different purposes, but mostly categorized into the following two categories. Data lakes is a term used to represent disconnected but relevant data that are used by various business units wit...
Today most companies are adopting or evaluating container technology - Docker in particular - to speed up application deployment, drive down cost, ease management and make application delivery more flexible overall. As with most new architectures, this dream takes significant work to become a reality. Even when you do get your application componentized enough and packaged properly, there are still challenges for DevOps teams to making the shift to continuous delivery and achieving that reducti...
Most of the time there is a lot of work involved to move to the cloud, and most of that isn't really related to AWS or Azure or Google Cloud. Before we talk about public cloud vendors and DevOps tools, there are usually several technical and non-technical challenges that are connected to it and that every company needs to solve to move to the cloud. In his session at 21st Cloud Expo, Stefano Bellasio, CEO and founder of Cloud Academy Inc., will discuss what the tools, disciplines, and cultural...
Enterprises are moving to the cloud faster than most of us in security expected. CIOs are going from 0 to 100 in cloud adoption and leaving security teams in the dust. Once cloud is part of an enterprise stack, it’s unclear who has responsibility for the protection of applications, services, and data. When cloud breaches occur, whether active compromise or a publicly accessible database, the blame must fall on both service providers and users. In his session at 21st Cloud Expo, Ben Johnson, C...
21st International Cloud Expo, taking place October 31 - November 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA, will feature technical sessions from a rock star conference faculty and the leading industry players in the world. Cloud computing is now being embraced by a majority of enterprises of all sizes. Yesterday's debate about public vs. private has transformed into the reality of hybrid cloud: a recent survey shows that 74% of enterprises have a hybrid cloud strategy. Me...
‘Trend’ is a pretty common business term, but its definition tends to vary by industry. In performance monitoring, trend, or trend shift, is a key metric that is used to indicate change. Change is inevitable. Today’s websites must frequently update and change to keep up with competition and attract new users, but such changes can have a negative impact on the user experience if not managed properly. The dynamic nature of the Internet makes it necessary to constantly monitor different metrics. O...
Agile has finally jumped the technology shark, expanding outside the software world. Enterprises are now increasingly adopting Agile practices across their organizations in order to successfully navigate the disruptive waters that threaten to drown them. In our quest for establishing change as a core competency in our organizations, this business-centric notion of Agile is an essential component of Agile Digital Transformation. In the years since the publication of the Agile Manifesto, the conn...
Many organizations are now looking to DevOps maturity models to gauge their DevOps adoption and compare their maturity to their peers. However, as enterprise organizations rush to adopt DevOps, moving past experimentation to embrace it at scale, they are in danger of falling into the trap that they have fallen into time and time again. Unfortunately, we've seen this movie before, and we know how it ends: badly.
There is a huge demand for responsive, real-time mobile and web experiences, but current architectural patterns do not easily accommodate applications that respond to events in real time. Common solutions using message queues or HTTP long-polling quickly lead to resiliency, scalability and development velocity challenges. In his session at 21st Cloud Expo, Ryland Degnan, a Senior Software Engineer on the Netflix Edge Platform team, will discuss how by leveraging a reactive stream-based protocol,...
Many organizations adopt DevOps to reduce cycle times and deliver software faster; some take on DevOps to drive higher quality and better end-user experience; others look to DevOps for a clearer line-of-sight to customers to drive better business impacts. In truth, these three foundations go together. In this power panel at @DevOpsSummit 21st Cloud Expo, moderated by DevOps Conference Co-Chair Andi Mann, industry experts will discuss how leading organizations build application success from all...
The last two years has seen discussions about cloud computing evolve from the public / private / hybrid split to the reality that most enterprises will be creating a complex, multi-cloud strategy. Companies are wary of committing all of their resources to a single cloud, and instead are choosing to spread the risk – and the benefits – of cloud computing across multiple providers and internal infrastructures, as they follow their business needs. Will this approach be successful? How large is the ...
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
"NetApp's vision is how we help organizations manage data - delivering the right data in the right place, in the right time, to the people who need it, and doing it agnostic to what the platform is," explained Josh Atwell, Developer Advocate for NetApp, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...
One of the biggest challenges with adopting a DevOps mentality is: new applications are easily adapted to cloud-native, microservice-based, or containerized architectures - they can be built for them - but old applications need complex refactoring. On the other hand, these new technologies can require relearning or adapting new, oftentimes more complex, methodologies and tools to be ready for production. In his general session at @DevOpsSummit at 20th Cloud Expo, Chris Brown, Solutions Marketi...