1 / 2

Agile Administration in Tooling and Tool Integration | Agile Scrum Master Certification - World Of Agile

Tools are inherent to our jobs, inherent to how we solve the problems we face each day. Our comfort level with the set of tools that are available to us, and our ability to adapt to new tools as they evolve and shape our thoughts and ideas. While it is possible to manage servers by hand, or even artisinally crafted shell scripts, a proper configuration management tool is invaluable especially as your environment and team changes.

Download Presentation

Agile Administration in Tooling and Tool Integration | Agile Scrum Master Certification - World Of Agile

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1.   Agile Administration in Tooling and Tool Integration | Agile  Scrum Master Certification - World Of Agile    Tools are inherent to our jobs, inherent to how we solve the problems we  face each day. Our comfort level with the set of tools that are available to  us, and our ability to adapt to new tools as they evolve and shape our  thoughts and ideas. The availability of collective knowledge within the  palm of your hand combined with the collaboration across organization  and company boundaries through open source software is dramatically  disrupting the status quo of work. Companies mired in managing  infrastructure configuration management by hand with unknown numbers  of divergent systems, unable to quickly change and respond to market  demands will struggle against their counterparts who have managed to  contain their complexity on one axis through infrastructure automation.  While it is possible to manage servers by hand, or even artisanally crafted  shell scripts, a proper configuration management tool is invaluable  especially as your environment and team changes.    Even the best software developers will struggle if they are working in an  environment without a version control system in place. Tools matter in  that not having them, or using them incorrectly, can destroy the  effectiveness of even the most intelligent and empathetic of engineers.  The consideration you give to the tools you use in your organization will  reflect in the overall organization’s success. You’ll find that what is a good  tool for some teams might not be a good one for others. The strength of  tools comes from how well they fit the needs of the people or groups using  them. If you don’t need feature X, its presence won’t be a selling point  when considering which tool your organization should use. Especially in  larger organizations with teams numbering in the dozens, finding one tool  that meets the needs of every team will be increasingly difficult. You will  have to strike a balance between deciding on one tool that will be used  across the entire company consistently and allowing more freedom of  choice among individual teams. There are benefits to both the consistency  and manageability that comes from having only one tool in use in an  organization, and also from allowing teams to pick specific tools that work  best for then.     

  2. Because ​Agile​ is a cultural shift and collaboration, there is no single "Agile  tool": it is rather a set, consisting of multiple tools in the Delivery and  Deployment pipelines. Generally, Agile tools fit into one or more of these  categories, which is reflective of the software development and delivery  process:    ● Plan – Plan testing strategy, CI/CI Strategy, Choice of Tools etc  ● Code — Code development and review, version control tools, code  merging;  ● Build — Continuous integration tools, build status;  ● Test — Test and results determine performance;  ● Release — Change management, release approvals, release  automation;  ● Deploy — Infrastructure configuration and management,  Infrastructure–as–Code tools;  ● Operate and Monitor — Applications performance monitoring,  end–user experience.    Though there are many tools available, certain categories of them are  essential in the toolchain setup for use in an organization.    Tools such as Docker (containerization), ​Jenkins​ (continuous integration),  Puppet (Infrastructure-as-Code) and Vagrant (virtualization  platform)—among many others—are often used and frequently referenced  in DevOps tooling discussions.    Typical stages in a toolchain looks like this which is typically referred to as  a ​DevOps Toolchain​ rather than just an Agile Toolchain.    For More Information, Follow the Links below-    Website - ​https://worldofagile.com/  Facebook - ​https://www.facebook.com/Fascinating.World.Of.Agile/  Twitter -​ https://twitter.com/WorldOfAgile  LinkedIn - ​https://www.linkedin.com/company/world-of-agile/  YouTube - ​https://www.youtube.com/c/WorldOfAgile 

More Related