To Know
-
No formulas
Celfocus Agile and DevOps
CALL To Science
—
Nov 2017
The business world is changing at an accelerating pace: it demands more and more effectiveness (solving customer needs and seizing business opportunities) and a relentless focus on efficiency (technical excellence, higher quality, safer and shorter time to market). Use technology to solve complex problems in a more efficient way.
Many ideas were experimented with success, achieved maturity and started growing organically in Big IT companies (Google, Microsoft, Facebook, Amazon, Uber, etc…) making them much more competitive and innovative in comparison to others. Ideas such as Agile development, DevOps, Continuous Integration, Continuous Delivery, Infrastructure as Code, Test Driven Development, Cloud come with a common objective:
Celfocus’ Agile and DevOps Transformation is starting and we aim to achieve a level of maturity, grow organically to encompass several parts of these techniques and methodologies in a flexible and smooth way. The sentence that we choose to define our Celfocus Agile and & DevOps way is “A People-Centric and disciplined approach to continuously deliver value to customers in an agile way.”
For many years, Celfocus followed a project based approach using Waterfall. Our goal is not to stop doing it, we want to have a strong support of a dual delivery model (waterfall and Agile) in order to adapt the best process according to the context. There’s no one model fits all, what we do well we need to preserve and keep evolving. Agile is not new at Celfocus, several initiatives have already taken place in the past, examples like EOL or GCC provide us with best practices and lessons learned to apply for future projects. However, if we want to create a supportive culture of agile we need to expand the knowledge and share these examples across the organisation creating a learning organization.
So first let’s clarify in a simple sentence the meaning of each technique and methodology:
Agile is focused on value. It’s a collaboration methodology, with a cross functional team that works on a very interactive (constant inspect and adapt work) and iterative (small and often development cycles) way to deliver the highest value to customers in the shortest time possible. Within Agile there are several frameworks such as Scrum, Kanban, RAD, AUP, ASP, etc.
In the beginning of agile, teams missed the “last mile”(put in production as fast as is developed). Several techniques and operations were developed to make the entire process more efficient. Joining Agile with these techniques was named DevOps, we can name it Agile 2.0 as well ☺︎
DevOps combines the cultural and technical philosophies of software development, quality assurance, and IT/InfoSec operations into a single system of systems that is managed as a whole. The purpose is to deliver applications and support services at a much higher velocity and efficiency.
CI (Continuous integration): Software development practice where team members integrate their work frequently, leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible.
Continuous Delivery: is the ability to get changes of all types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way.
Cloud: Type of Internet-based computing that provides shared computer processing resources and data to computers and other devices on demand.
Infrastructure as a service (IaaS): online services that abstract the user from the details of infrastructure like physical computing resources, location, data partitioning, scaling, security, backup etc.
Platform as a service (PaaS): development environment to application developers. Cloud providers deliver a computing platform, typically including operating system, programming-language execution environment, database, and web server.
Test Driven Development (TDD): TDD is a software development process that relies on the repetition of a very short development cycle: Requirements are turned into very specific test cases, then the software is improved to pass the new tests, only.
Culture: Change our attitude
Code: Change the way we code
Normally when we hear about DevOps, we think about tools, yes it’s important but most importantly are the people. This is a cultural change and if we aren’t open to change or a new collaboration model, there’s no Agile or DevOps.
To see the meaning of each item, please consult our guide here.
Being part of an IT organization means we hear the word “transformation” daily, perhaps even more frequently. Like other well-worn terms such as “Digitization,” “DevOps,” or “Agile,” transformation can mean a lot of different things depending on the specific organization, the team, or the individual person saying or hearing it. At its core, though, transformation is not an empty concept — far from it! And for us it means Creating a Supportive agile culture in Celfocus evolving from a “doing agile” in isolated projects to “being agile”.
What’s the differences between Agile (Value driven) and Waterfall (Plan driven)?
First items to assess:
Cynefin is a decision framework that recognises the causal differences that exist between systems, proposing new approaches to decision making in complex social environments. Agile is more adequate for Complex problems but also fits well with complicated. Waterfall is more oriented for complicated and Simple problems. There no best methodology to cover chaotic problems!!
Just bear in mind: there isn’t a magic formula. It’s all about collaboration, continuous, daily improvement—the constant discipline of pursuing higher performance.
The business world is changing at an accelerating pace: it demands more and more effectiveness (solving customer needs and seizing business opportunities) and a relentless focus on efficiency (technical excellence, higher quality, safer and shorter time to market). Use technology to solve complex problems in a more efficient way.
Many ideas were experimented with success, achieved maturity and started growing organically in Big IT companies (Google, Microsoft, Facebook, Amazon, Uber, etc…) making them much more competitive and innovative in comparison to others. Ideas such as Agile development, DevOps, Continuous Integration, Continuous Delivery, Infrastructure as Code, Test Driven Development, Cloud come with a common objective:
Celfocus’ Agile and DevOps Transformation is starting and we aim to achieve a level of maturity, grow organically to encompass several parts of these techniques and methodologies in a flexible and smooth way. The sentence that we choose to define our Celfocus Agile and & DevOps way is “A People-Centric and disciplined approach to continuously deliver value to customers in an agile way.”
For many years, Celfocus followed a project based approach using Waterfall. Our goal is not to stop doing it, we want to have a strong support of a dual delivery model (waterfall and Agile) in order to adapt the best process according to the context. There’s no one model fits all, what we do well we need to preserve and keep evolving. Agile is not new at Celfocus, several initiatives have already taken place in the past, examples like EOL or GCC provide us with best practices and lessons learned to apply for future projects. However, if we want to create a supportive culture of agile we need to expand the knowledge and share these examples across the organisation creating a learning organization.
So first let’s clarify in a simple sentence the meaning of each technique and methodology:
Agile is focused on value. It’s a collaboration methodology, with a cross functional team that works on a very interactive (constant inspect and adapt work) and iterative (small and often development cycles) way to deliver the highest value to customers in the shortest time possible. Within Agile there are several frameworks such as Scrum, Kanban, RAD, AUP, ASP, etc.
In the beginning of agile, teams missed the “last mile”(put in production as fast as is developed). Several techniques and operations were developed to make the entire process more efficient. Joining Agile with these techniques was named DevOps, we can name it Agile 2.0 as well ☺︎
DevOps combines the cultural and technical philosophies of software development, quality assurance, and IT/InfoSec operations into a single system of systems that is managed as a whole. The purpose is to deliver applications and support services at a much higher velocity and efficiency.
CI (Continuous integration): Software development practice where team members integrate their work frequently, leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible.
Continuous Delivery: is the ability to get changes of all types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way.
Cloud: Type of Internet-based computing that provides shared computer processing resources and data to computers and other devices on demand.
Infrastructure as a service (IaaS): online services that abstract the user from the details of infrastructure like physical computing resources, location, data partitioning, scaling, security, backup etc.
Platform as a service (PaaS): development environment to application developers. Cloud providers deliver a computing platform, typically including operating system, programming-language execution environment, database, and web server.
Test Driven Development (TDD): TDD is a software development process that relies on the repetition of a very short development cycle: Requirements are turned into very specific test cases, then the software is improved to pass the new tests, only.
Culture: Change our attitude
Code: Change the way we code
Normally when we hear about DevOps, we think about tools, yes it’s important but most importantly are the people. This is a cultural change and if we aren’t open to change or a new collaboration model, there’s no Agile or DevOps.
To see the meaning of each item, please consult our guide here.
Being part of an IT organization means we hear the word “transformation” daily, perhaps even more frequently. Like other well-worn terms such as “Digitization,” “DevOps,” or “Agile,” transformation can mean a lot of different things depending on the specific organization, the team, or the individual person saying or hearing it. At its core, though, transformation is not an empty concept — far from it! And for us it means Creating a Supportive agile culture in Celfocus evolving from a “doing agile” in isolated projects to “being agile”.
What’s the differences between Agile (Value driven) and Waterfall (Plan driven)?
First items to assess:
Cynefin is a decision framework that recognises the causal differences that exist between systems, proposing new approaches to decision making in complex social environments. Agile is more adequate for Complex problems but also fits well with complicated. Waterfall is more oriented for complicated and Simple problems. There no best methodology to cover chaotic problems!!
Just bear in mind: there isn’t a magic formula. It’s all about collaboration, continuous, daily improvement—the constant discipline of pursuing higher performance.
The business world is changing at an accelerating pace: it demands more and more effectiveness (solving customer needs and seizing business opportunities) and a relentless focus on efficiency (technical excellence, higher quality, safer and shorter time to market). Use technology to solve complex problems in a more efficient way.
Many ideas were experimented with success, achieved maturity and started growing organically in Big IT companies (Google, Microsoft, Facebook, Amazon, Uber, etc…) making them much more competitive and innovative in comparison to others. Ideas such as Agile development, DevOps, Continuous Integration, Continuous Delivery, Infrastructure as Code, Test Driven Development, Cloud come with a common objective:
Celfocus’ Agile and DevOps Transformation is starting and we aim to achieve a level of maturity, grow organically to encompass several parts of these techniques and methodologies in a flexible and smooth way. The sentence that we choose to define our Celfocus Agile and & DevOps way is “A People-Centric and disciplined approach to continuously deliver value to customers in an agile way.”
For many years, Celfocus followed a project based approach using Waterfall. Our goal is not to stop doing it, we want to have a strong support of a dual delivery model (waterfall and Agile) in order to adapt the best process according to the context. There’s no one model fits all, what we do well we need to preserve and keep evolving. Agile is not new at Celfocus, several initiatives have already taken place in the past, examples like EOL or GCC provide us with best practices and lessons learned to apply for future projects. However, if we want to create a supportive culture of agile we need to expand the knowledge and share these examples across the organisation creating a learning organization.
So first let’s clarify in a simple sentence the meaning of each technique and methodology:
Agile is focused on value. It’s a collaboration methodology, with a cross functional team that works on a very interactive (constant inspect and adapt work) and iterative (small and often development cycles) way to deliver the highest value to customers in the shortest time possible. Within Agile there are several frameworks such as Scrum, Kanban, RAD, AUP, ASP, etc.
In the beginning of agile, teams missed the “last mile”(put in production as fast as is developed). Several techniques and operations were developed to make the entire process more efficient. Joining Agile with these techniques was named DevOps, we can name it Agile 2.0 as well ☺︎
DevOps combines the cultural and technical philosophies of software development, quality assurance, and IT/InfoSec operations into a single system of systems that is managed as a whole. The purpose is to deliver applications and support services at a much higher velocity and efficiency.
CI (Continuous integration): Software development practice where team members integrate their work frequently, leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible.
Continuous Delivery: is the ability to get changes of all types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way.
Cloud: Type of Internet-based computing that provides shared computer processing resources and data to computers and other devices on demand.
Infrastructure as a service (IaaS): online services that abstract the user from the details of infrastructure like physical computing resources, location, data partitioning, scaling, security, backup etc.
Platform as a service (PaaS): development environment to application developers. Cloud providers deliver a computing platform, typically including operating system, programming-language execution environment, database, and web server.
Test Driven Development (TDD): TDD is a software development process that relies on the repetition of a very short development cycle: Requirements are turned into very specific test cases, then the software is improved to pass the new tests, only.
Culture: Change our attitude
Code: Change the way we code
Normally when we hear about DevOps, we think about tools, yes it’s important but most importantly are the people. This is a cultural change and if we aren’t open to change or a new collaboration model, there’s no Agile or DevOps.
To see the meaning of each item, please consult our guide here.
Being part of an IT organization means we hear the word “transformation” daily, perhaps even more frequently. Like other well-worn terms such as “Digitization,” “DevOps,” or “Agile,” transformation can mean a lot of different things depending on the specific organization, the team, or the individual person saying or hearing it. At its core, though, transformation is not an empty concept — far from it! And for us it means Creating a Supportive agile culture in Celfocus evolving from a “doing agile” in isolated projects to “being agile”.
What’s the differences between Agile (Value driven) and Waterfall (Plan driven)?
First items to assess:
Cynefin is a decision framework that recognises the causal differences that exist between systems, proposing new approaches to decision making in complex social environments. Agile is more adequate for Complex problems but also fits well with complicated. Waterfall is more oriented for complicated and Simple problems. There no best methodology to cover chaotic problems!!
Just bear in mind: there isn’t a magic formula. It’s all about collaboration, continuous, daily improvement—the constant discipline of pursuing higher performance.
.png)
