�ݺ�ߣshows by User: tstiehm

�ݺ�ߣshows by User: tstiehm / http://www.slideshare.net/images/logo.gif �ݺ�ߣshows by User: tstiehm / Tue, 01 Oct 2024 12:15:24 GMT �ݺ�ߣShare feed for �ݺ�ߣshows by User: tstiehm AgileDC 2024 Agile Software Development Antipatterns and how to avoid them. /slideshow/agiledc-2024-agile-software-development-antipatterns-and-how-to-avoid-them/272126658 agiledc2024-agilesoftwaredevelopmentantipatterns-241001121524-cb43e222
Software development is hard and poorly implemented or broken tools, techniques, and patterns just make it worse. Learn to spot software development anti-patterns and how to work your way back to a sane way of working. Antipatterns can be hard to recognize and mitigate because they are solutions to problems. They can appear to solve the problem in the short run. The problem is that they create long-term consequences that are worse than the short-term problems you avoid by using them. Continuous Build is an antipattern that I have often seen where a team will have a Continuous Integration (CI) in place but it only builds the code. No code integration tests are run and health metrics are collected. While this is better than not building automatically, it leaves a lot of health check information out. Without this information, you never gain the confidence that your build is healthy. The whole point of CI is the confidence that your build is healthy. You aren’t doing CI if you can’t get that confidence with test automation and code quality analysis. Just like CI, other software development practices can be hard to understand, implement, and get right. Even with the best of intentions, we make mistakes or misinterpret the implementation of a technique. Learn how to spot common software development anti-patterns and how to correct them. We have all experienced a time when we wanted to believe we could make an antipattern work but it never does. It is better to learn how to spot these and how to correct them than it is to try to keep tweaking a broken process hoping this time it will be better.]]>
Software development is hard and poorly implemented or broken tools, techniques, and patterns just make it worse. Learn to spot software development anti-patterns and how to work your way back to a sane way of working. Antipatterns can be hard to recognize and mitigate because they are solutions to problems. They can appear to solve the problem in the short run. The problem is that they create long-term consequences that are worse than the short-term problems you avoid by using them. Continuous Build is an antipattern that I have often seen where a team will have a Continuous Integration (CI) in place but it only builds the code. No code integration tests are run and health metrics are collected. While this is better than not building automatically, it leaves a lot of health check information out. Without this information, you never gain the confidence that your build is healthy. The whole point of CI is the confidence that your build is healthy. You aren’t doing CI if you can’t get that confidence with test automation and code quality analysis. Just like CI, other software development practices can be hard to understand, implement, and get right. Even with the best of intentions, we make mistakes or misinterpret the implementation of a technique. Learn how to spot common software development anti-patterns and how to correct them. We have all experienced a time when we wanted to believe we could make an antipattern work but it never does. It is better to learn how to spot these and how to correct them than it is to try to keep tweaking a broken process hoping this time it will be better.]]> Tue, 01 Oct 2024 12:15:24 GMT /slideshow/agiledc-2024-agile-software-development-antipatterns-and-how-to-avoid-them/272126658 tstiehm@slideshare.net(tstiehm) AgileDC 2024 Agile Software Development Antipatterns and how to avoid them. tstiehm Software development is hard and poorly implemented or broken tools, techniques, and patterns just make it worse. Learn to spot software development anti-patterns and how to work your way back to a sane way of working. Antipatterns can be hard to recognize and mitigate because they are solutions to problems. They can appear to solve the problem in the short run. The problem is that they create long-term consequences that are worse than the short-term problems you avoid by using them. Continuous Build is an antipattern that I have often seen where a team will have a Continuous Integration (CI) in place but it only builds the code. No code integration tests are run and health metrics are collected. While this is better than not building automatically, it leaves a lot of health check information out. Without this information, you never gain the confidence that your build is healthy. The whole point of CI is the confidence that your build is healthy. You aren’t doing CI if you can’t get that confidence with test automation and code quality analysis. Just like CI, other software development practices can be hard to understand, implement, and get right. Even with the best of intentions, we make mistakes or misinterpret the implementation of a technique. Learn how to spot common software development anti-patterns and how to correct them. We have all experienced a time when we wanted to believe we could make an antipattern work but it never does. It is better to learn how to spot these and how to correct them than it is to try to keep tweaking a broken process hoping this time it will be better. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/agiledc2024-agilesoftwaredevelopmentantipatterns-241001121524-cb43e222-thumbnail.jpg?width=120&height=120&fit=bounds" /> Software development is hard and poorly implemented or broken tools, techniques, and patterns just make it worse. Learn to spot software development anti-patterns and how to work your way back to a sane way of working. Antipatterns can be hard to recognize and mitigate because they are solutions to problems. They can appear to solve the problem in the short run. The problem is that they create long-term consequences that are worse than the short-term problems you avoid by using them. Continuous Build is an antipattern that I have often seen where a team will have a Continuous Integration (CI) in place but it only builds the code. No code integration tests are run and health metrics are collected. While this is better than not building automatically, it leaves a lot of health check information out. Without this information, you never gain the confidence that your build is healthy. The whole point of CI is the confidence that your build is healthy. You aren’t doing CI if you can’t get that confidence with test automation and code quality analysis. Just like CI, other software development practices can be hard to understand, implement, and get right. Even with the best of intentions, we make mistakes or misinterpret the implementation of a technique. Learn how to spot common software development anti-patterns and how to correct them. We have all experienced a time when we wanted to believe we could make an antipattern work but it never does. It is better to learn how to spot these and how to correct them than it is to try to keep tweaking a broken process hoping this time it will be better.

AgileDC 2024 Agile Software Development Antipatterns and how to avoid them. from Tom Stiehm

]]> 9 0 https://cdn.slidesharecdn.com/ss_thumbnails/agiledc2024-agilesoftwaredevelopmentantipatterns-241001121524-cb43e222-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Agile Software Development Antipatterns and how to avoid them /slideshow/agile-software-development-antipatterns-and-how-to-avoid-them/271279124 agile2024-agilesoftwaredevelopmentantipatterns-240824201057-e6d2a594
Software development is hard and poorly implemented or broken tools, techniques, and patterns just make it worse. Learn to spot software development anti-patterns and how to work your way back to a sane way of working. Antipatterns can be hard to recognize and mitigate because they are solutions to problems. They can appear to solve the problem in the short run. The problem is that they create long-term consequences that are worse than the short-term problems you avoid by using them. Continuous Build is an antipattern that I have often seen where a team will have a Continuous Integration (CI) in place but it only builds the code. No code integration tests are run and health metrics are collected. While this is better than not building automatically, it leaves a lot of health check information out. Without this information, you never gain the confidence that your build is healthy. The whole point of CI is the confidence that your build is healthy. You aren’t doing CI if you can’t get that confidence with test automation and code quality analysis. Just like CI, other software development practices can be hard to understand, implement, and get right. Even with the best of intentions, we make mistakes or misinterpret the implementation of a technique. Learn how to spot common software development anti-patterns and how to correct them.]]>
Software development is hard and poorly implemented or broken tools, techniques, and patterns just make it worse. Learn to spot software development anti-patterns and how to work your way back to a sane way of working. Antipatterns can be hard to recognize and mitigate because they are solutions to problems. They can appear to solve the problem in the short run. The problem is that they create long-term consequences that are worse than the short-term problems you avoid by using them. Continuous Build is an antipattern that I have often seen where a team will have a Continuous Integration (CI) in place but it only builds the code. No code integration tests are run and health metrics are collected. While this is better than not building automatically, it leaves a lot of health check information out. Without this information, you never gain the confidence that your build is healthy. The whole point of CI is the confidence that your build is healthy. You aren’t doing CI if you can’t get that confidence with test automation and code quality analysis. Just like CI, other software development practices can be hard to understand, implement, and get right. Even with the best of intentions, we make mistakes or misinterpret the implementation of a technique. Learn how to spot common software development anti-patterns and how to correct them.]]> Sat, 24 Aug 2024 20:10:56 GMT /slideshow/agile-software-development-antipatterns-and-how-to-avoid-them/271279124 tstiehm@slideshare.net(tstiehm) Agile Software Development Antipatterns and how to avoid them tstiehm Software development is hard and poorly implemented or broken tools, techniques, and patterns just make it worse. Learn to spot software development anti-patterns and how to work your way back to a sane way of working. Antipatterns can be hard to recognize and mitigate because they are solutions to problems. They can appear to solve the problem in the short run. The problem is that they create long-term consequences that are worse than the short-term problems you avoid by using them. Continuous Build is an antipattern that I have often seen where a team will have a Continuous Integration (CI) in place but it only builds the code. No code integration tests are run and health metrics are collected. While this is better than not building automatically, it leaves a lot of health check information out. Without this information, you never gain the confidence that your build is healthy. The whole point of CI is the confidence that your build is healthy. You aren’t doing CI if you can’t get that confidence with test automation and code quality analysis. Just like CI, other software development practices can be hard to understand, implement, and get right. Even with the best of intentions, we make mistakes or misinterpret the implementation of a technique. Learn how to spot common software development anti-patterns and how to correct them. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/agile2024-agilesoftwaredevelopmentantipatterns-240824201057-e6d2a594-thumbnail.jpg?width=120&height=120&fit=bounds" /> Software development is hard and poorly implemented or broken tools, techniques, and patterns just make it worse. Learn to spot software development anti-patterns and how to work your way back to a sane way of working. Antipatterns can be hard to recognize and mitigate because they are solutions to problems. They can appear to solve the problem in the short run. The problem is that they create long-term consequences that are worse than the short-term problems you avoid by using them. Continuous Build is an antipattern that I have often seen where a team will have a Continuous Integration (CI) in place but it only builds the code. No code integration tests are run and health metrics are collected. While this is better than not building automatically, it leaves a lot of health check information out. Without this information, you never gain the confidence that your build is healthy. The whole point of CI is the confidence that your build is healthy. You aren’t doing CI if you can’t get that confidence with test automation and code quality analysis. Just like CI, other software development practices can be hard to understand, implement, and get right. Even with the best of intentions, we make mistakes or misinterpret the implementation of a technique. Learn how to spot common software development anti-patterns and how to correct them.

Agile Software Development Antipatterns and how to avoid them from Tom Stiehm

]]> 19 0 https://cdn.slidesharecdn.com/ss_thumbnails/agile2024-agilesoftwaredevelopmentantipatterns-240824201057-e6d2a594-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Shifting security all day dev ops /slideshow/shifting-security-all-day-dev-ops/191104192 shiftingsecurityalldaydevops-191106173518
All Day DevOps presentation on shifting security left. Learn more about why shifting left is the real innovation of DevSecOps and where to start.]]>
All Day DevOps presentation on shifting security left. Learn more about why shifting left is the real innovation of DevSecOps and where to start.]]> Wed, 06 Nov 2019 17:35:18 GMT /slideshow/shifting-security-all-day-dev-ops/191104192 tstiehm@slideshare.net(tstiehm) Shifting security all day dev ops tstiehm All Day DevOps presentation on shifting security left. Learn more about why shifting left is the real innovation of DevSecOps and where to start. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/shiftingsecurityalldaydevops-191106173518-thumbnail.jpg?width=120&height=120&fit=bounds" /> All Day DevOps presentation on shifting security left. Learn more about why shifting left is the real innovation of DevSecOps and where to start.

Shifting security all day dev ops from Tom Stiehm

]]> 120 1 https://cdn.slidesharecdn.com/ss_thumbnails/shiftingsecurityalldaydevops-191106173518-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Shifting Security Left - The Innovation of DevSecOps - ValleyTechCon /slideshow/shifting-security-left-the-innovation-of-devsecops-valleytechcon/176347061 shiftingsecurityvalleytechcon-190926135622
DevSecOps adds on the DevOps by making Application Security part of the daily workflow of the team in order to improve the quality and security of a product. Shift AppSec practices left is the key enabler to making AppSec a first-class citizen in the development effort rather than an afterthought with limited ability to be successful.]]>
DevSecOps adds on the DevOps by making Application Security part of the daily workflow of the team in order to improve the quality and security of a product. Shift AppSec practices left is the key enabler to making AppSec a first-class citizen in the development effort rather than an afterthought with limited ability to be successful.]]> Thu, 26 Sep 2019 13:56:22 GMT /slideshow/shifting-security-left-the-innovation-of-devsecops-valleytechcon/176347061 tstiehm@slideshare.net(tstiehm) Shifting Security Left - The Innovation of DevSecOps - ValleyTechCon tstiehm DevSecOps adds on the DevOps by making Application Security part of the daily workflow of the team in order to improve the quality and security of a product. Shift AppSec practices left is the key enabler to making AppSec a first-class citizen in the development effort rather than an afterthought with limited ability to be successful. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/shiftingsecurityvalleytechcon-190926135622-thumbnail.jpg?width=120&height=120&fit=bounds" /> DevSecOps adds on the DevOps by making Application Security part of the daily workflow of the team in order to improve the quality and security of a product. Shift AppSec practices left is the key enabler to making AppSec a first-class citizen in the development effort rather than an afterthought with limited ability to be successful.

Shifting Security Left - The Innovation of DevSecOps - ValleyTechCon from Tom Stiehm

]]> 424 0 https://cdn.slidesharecdn.com/ss_thumbnails/shiftingsecurityvalleytechcon-190926135622-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Shifting Security Left - The Innovation of DevSecOps - AgileDC /slideshow/shifting-security-left-the-innovation-of-devsecops-agiledc/175735465 shiftingsecurityleftagiledc-190925003704
Shifting AppSec practices left allows development teams to reduce risk and reduce the likelihood of getting exploited by a security defect.]]>
Shifting AppSec practices left allows development teams to reduce risk and reduce the likelihood of getting exploited by a security defect.]]> Wed, 25 Sep 2019 00:37:04 GMT /slideshow/shifting-security-left-the-innovation-of-devsecops-agiledc/175735465 tstiehm@slideshare.net(tstiehm) Shifting Security Left - The Innovation of DevSecOps - AgileDC tstiehm Shifting AppSec practices left allows development teams to reduce risk and reduce the likelihood of getting exploited by a security defect. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/shiftingsecurityleftagiledc-190925003704-thumbnail.jpg?width=120&height=120&fit=bounds" /> Shifting AppSec practices left allows development teams to reduce risk and reduce the likelihood of getting exploited by a security defect.

Shifting Security Left - The Innovation of DevSecOps - AgileDC from Tom Stiehm

]]> 178 0 https://cdn.slidesharecdn.com/ss_thumbnails/shiftingsecurityleftagiledc-190925003704-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Shifting Security Left from the Lean+Agile 2019 Conference /slideshow/shifting-security-left-from-the-leanagile-2019-conference/152470313 shiftingsecurityleftleanagile-190628195746
DevSecOps changes the application security value proposition by leveraging DevOps principles to shift security practices left and automating the collection of security-related data.]]>
DevSecOps changes the application security value proposition by leveraging DevOps principles to shift security practices left and automating the collection of security-related data.]]> Fri, 28 Jun 2019 19:57:46 GMT /slideshow/shifting-security-left-from-the-leanagile-2019-conference/152470313 tstiehm@slideshare.net(tstiehm) Shifting Security Left from the Lean+Agile 2019 Conference tstiehm DevSecOps changes the application security value proposition by leveraging DevOps principles to shift security practices left and automating the collection of security-related data. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/shiftingsecurityleftleanagile-190628195746-thumbnail.jpg?width=120&height=120&fit=bounds" /> DevSecOps changes the application security value proposition by leveraging DevOps principles to shift security practices left and automating the collection of security-related data.

Shifting Security Left from the Lean+Agile 2019 Conference from Tom Stiehm

]]> 183 1 https://cdn.slidesharecdn.com/ss_thumbnails/shiftingsecurityleftleanagile-190628195746-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Failure is inevitable but it isn't permanent /slideshow/failure-is-inevitable-but-it-isnt-permanent/120331742 failureisinevitablebutitisntpermanent-181022182226
Agile Transformation is harder than it needs to be because we often find ways to consciously or subconsciously sabotage our efforts if we can recognize this behavior it is possible to intervene and make a change for the positive.]]>
Agile Transformation is harder than it needs to be because we often find ways to consciously or subconsciously sabotage our efforts if we can recognize this behavior it is possible to intervene and make a change for the positive.]]> Mon, 22 Oct 2018 18:22:25 GMT /slideshow/failure-is-inevitable-but-it-isnt-permanent/120331742 tstiehm@slideshare.net(tstiehm) Failure is inevitable but it isn't permanent tstiehm Agile Transformation is harder than it needs to be because we often find ways to consciously or subconsciously sabotage our efforts if we can recognize this behavior it is possible to intervene and make a change for the positive. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/failureisinevitablebutitisntpermanent-181022182226-thumbnail.jpg?width=120&height=120&fit=bounds" /> Agile Transformation is harder than it needs to be because we often find ways to consciously or subconsciously sabotage our efforts if we can recognize this behavior it is possible to intervene and make a change for the positive.

Failure is inevitable but it isn't permanent from Tom Stiehm

]]> 201 2 https://cdn.slidesharecdn.com/ss_thumbnails/failureisinevitablebutitisntpermanent-181022182226-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Agile testing for embedded software development /slideshow/agile-testing-for-embedded-software-development/78683910 agiletestingforembeddedsoftwaredevelopment-170809025646
A large part of the success of agile adoptions is due to the automated testing approach used in agile projects. Because many of these techniques were pioneered in the development of web applications it can be hard to see how these techniques can be leveraged for a project where the software being built is for an embedded application. Discover ways to leverage agile testing techniques for embedded systems. Whether you are building a medical device, embedded controller, or Internet of Things device learn how to leverage these testing practices to create fully automated tests that fit into a DevOps build pipeline and help your team create higher quality, more reliable software. Test automation is the best way to maintain and execute a comprehensive suite of regression tests that allows you to take back control of your testing process while increasing test coverage. Learn how to be in control of your test process by stepping up your test automation to the next level. Embedded development and Internet of Things development is often done on platforms that lack modern software development and test automation tools. The more esoteric or the smaller the target audience, the less likely tool vendors are to create products that directly support the deployment environment. This can make getting started with test automation using older tools that are not as actively supported by vendors can be a challenge that has to be overcome by a team that wants to move toward a Continuous Deployment process. This session is aimed at people that are trying to adopt agile and continuous delivery with embedded technology, but might be worried that it can’t work in their particular environment due to their industry, technology stack, culture, or regulatory environment. ]]>
A large part of the success of agile adoptions is due to the automated testing approach used in agile projects. Because many of these techniques were pioneered in the development of web applications it can be hard to see how these techniques can be leveraged for a project where the software being built is for an embedded application. Discover ways to leverage agile testing techniques for embedded systems. Whether you are building a medical device, embedded controller, or Internet of Things device learn how to leverage these testing practices to create fully automated tests that fit into a DevOps build pipeline and help your team create higher quality, more reliable software. Test automation is the best way to maintain and execute a comprehensive suite of regression tests that allows you to take back control of your testing process while increasing test coverage. Learn how to be in control of your test process by stepping up your test automation to the next level. Embedded development and Internet of Things development is often done on platforms that lack modern software development and test automation tools. The more esoteric or the smaller the target audience, the less likely tool vendors are to create products that directly support the deployment environment. This can make getting started with test automation using older tools that are not as actively supported by vendors can be a challenge that has to be overcome by a team that wants to move toward a Continuous Deployment process. This session is aimed at people that are trying to adopt agile and continuous delivery with embedded technology, but might be worried that it can’t work in their particular environment due to their industry, technology stack, culture, or regulatory environment. ]]> Wed, 09 Aug 2017 02:56:46 GMT /slideshow/agile-testing-for-embedded-software-development/78683910 tstiehm@slideshare.net(tstiehm) Agile testing for embedded software development tstiehm A large part of the success of agile adoptions is due to the automated testing approach used in agile projects. Because many of these techniques were pioneered in the development of web applications it can be hard to see how these techniques can be leveraged for a project where the software being built is for an embedded application. Discover ways to leverage agile testing techniques for embedded systems. Whether you are building a medical device, embedded controller, or Internet of Things device learn how to leverage these testing practices to create fully automated tests that fit into a DevOps build pipeline and help your team create higher quality, more reliable software. Test automation is the best way to maintain and execute a comprehensive suite of regression tests that allows you to take back control of your testing process while increasing test coverage. Learn how to be in control of your test process by stepping up your test automation to the next level. Embedded development and Internet of Things development is often done on platforms that lack modern software development and test automation tools. The more esoteric or the smaller the target audience, the less likely tool vendors are to create products that directly support the deployment environment. This can make getting started with test automation using older tools that are not as actively supported by vendors can be a challenge that has to be overcome by a team that wants to move toward a Continuous Deployment process. This session is aimed at people that are trying to adopt agile and continuous delivery with embedded technology, but might be worried that it can’t work in their particular environment due to their industry, technology stack, culture, or regulatory environment. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/agiletestingforembeddedsoftwaredevelopment-170809025646-thumbnail.jpg?width=120&height=120&fit=bounds" /> A large part of the success of agile adoptions is due to the automated testing approach used in agile projects. Because many of these techniques were pioneered in the development of web applications it can be hard to see how these techniques can be leveraged for a project where the software being built is for an embedded application. Discover ways to leverage agile testing techniques for embedded systems. Whether you are building a medical device, embedded controller, or Internet of Things device learn how to leverage these testing practices to create fully automated tests that fit into a DevOps build pipeline and help your team create higher quality, more reliable software. Test automation is the best way to maintain and execute a comprehensive suite of regression tests that allows you to take back control of your testing process while increasing test coverage. Learn how to be in control of your test process by stepping up your test automation to the next level. Embedded development and Internet of Things development is often done on platforms that lack modern software development and test automation tools. The more esoteric or the smaller the target audience, the less likely tool vendors are to create products that directly support the deployment environment. This can make getting started with test automation using older tools that are not as actively supported by vendors can be a challenge that has to be overcome by a team that wants to move toward a Continuous Deployment process. This session is aimed at people that are trying to adopt agile and continuous delivery with embedded technology, but might be worried that it can’t work in their particular environment due to their industry, technology stack, culture, or regulatory environment.

Agile testing for embedded software development from Tom Stiehm

]]> 632 4 https://cdn.slidesharecdn.com/ss_thumbnails/agiletestingforembeddedsoftwaredevelopment-170809025646-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Overcoming problems implementing cloud based dev ops for distributed agile projects /slideshow/overcoming-problems-implementing-cloud-based-dev-ops-for-distributed-agile-projects/27097393 overcomingproblemsimplementingcloud-baseddevopsfordistributedagileprojects-131011080323-phpapp01
Cloud-base development, delivery and deployment are the future of IT operations. Getting to the Cloud and conducting the business of IT there is a journey of change and growth to an IT Organization. Discover potential problems and their solutions based the experiences in developing Cloud-Based operations for multiple large, distributed projects in a variety of challenging environments. Overcoming these challenges is the key to successful adoption of Cloud DevOps and realizing the operational and productivity gains of the Cloud. Learn the hard earned lessons we learned from creating successful DevOps projects using Cloud Technology.]]>
Cloud-base development, delivery and deployment are the future of IT operations. Getting to the Cloud and conducting the business of IT there is a journey of change and growth to an IT Organization. Discover potential problems and their solutions based the experiences in developing Cloud-Based operations for multiple large, distributed projects in a variety of challenging environments. Overcoming these challenges is the key to successful adoption of Cloud DevOps and realizing the operational and productivity gains of the Cloud. Learn the hard earned lessons we learned from creating successful DevOps projects using Cloud Technology.]]> Fri, 11 Oct 2013 08:03:23 GMT /slideshow/overcoming-problems-implementing-cloud-based-dev-ops-for-distributed-agile-projects/27097393 tstiehm@slideshare.net(tstiehm) Overcoming problems implementing cloud based dev ops for distributed agile projects tstiehm Cloud-base development, delivery and deployment are the future of IT operations. Getting to the Cloud and conducting the business of IT there is a journey of change and growth to an IT Organization. Discover potential problems and their solutions based the experiences in developing Cloud-Based operations for multiple large, distributed projects in a variety of challenging environments. Overcoming these challenges is the key to successful adoption of Cloud DevOps and realizing the operational and productivity gains of the Cloud. Learn the hard earned lessons we learned from creating successful DevOps projects using Cloud Technology. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/overcomingproblemsimplementingcloud-baseddevopsfordistributedagileprojects-131011080323-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> Cloud-base development, delivery and deployment are the future of IT operations. Getting to the Cloud and conducting the business of IT there is a journey of change and growth to an IT Organization. Discover potential problems and their solutions based the experiences in developing Cloud-Based operations for multiple large, distributed projects in a variety of challenging environments. Overcoming these challenges is the key to successful adoption of Cloud DevOps and realizing the operational and productivity gains of the Cloud. Learn the hard earned lessons we learned from creating successful DevOps projects using Cloud Technology.

Overcoming problems implementing cloud based dev ops for distributed agile projects from Tom Stiehm

]]> 11040 5 https://cdn.slidesharecdn.com/ss_thumbnails/overcomingproblemsimplementingcloud-baseddevopsfordistributedagileprojects-131011080323-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Implementing cloud based devops for distributed agile projects /tstiehm/implementing-cloud-based-dev-ops-for-distributed-agile-projects-final implementingcloud-baseddevopsfordistributedagileprojects-final-130630201629-phpapp01
Cloud-based development, delivery and deployment environments are the future of IT operations, learn how to best leverage the Cloud to enable your teams to use it effectively and to give them an advantage. Learn why Cloud software delivery is different from traditional software delivery environments and how to optimize your platform and team to get the most out of the Cloud. Geographically distributed software delivery teams are now the norm for large projects and the Cloud is a perfect enabler to level the playing field for your distributed teams and give them all the same ability to achieve high productivity.]]>
Cloud-based development, delivery and deployment environments are the future of IT operations, learn how to best leverage the Cloud to enable your teams to use it effectively and to give them an advantage. Learn why Cloud software delivery is different from traditional software delivery environments and how to optimize your platform and team to get the most out of the Cloud. Geographically distributed software delivery teams are now the norm for large projects and the Cloud is a perfect enabler to level the playing field for your distributed teams and give them all the same ability to achieve high productivity.]]> Sun, 30 Jun 2013 20:16:29 GMT /tstiehm/implementing-cloud-based-dev-ops-for-distributed-agile-projects-final tstiehm@slideshare.net(tstiehm) Implementing cloud based devops for distributed agile projects tstiehm Cloud-based development, delivery and deployment environments are the future of IT operations, learn how to best leverage the Cloud to enable your teams to use it effectively and to give them an advantage. Learn why Cloud software delivery is different from traditional software delivery environments and how to optimize your platform and team to get the most out of the Cloud. Geographically distributed software delivery teams are now the norm for large projects and the Cloud is a perfect enabler to level the playing field for your distributed teams and give them all the same ability to achieve high productivity. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/implementingcloud-baseddevopsfordistributedagileprojects-final-130630201629-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> Cloud-based development, delivery and deployment environments are the future of IT operations, learn how to best leverage the Cloud to enable your teams to use it effectively and to give them an advantage. Learn why Cloud software delivery is different from traditional software delivery environments and how to optimize your platform and team to get the most out of the Cloud. Geographically distributed software delivery teams are now the norm for large projects and the Cloud is a perfect enabler to level the playing field for your distributed teams and give them all the same ability to achieve high productivity.

Implementing cloud based devops for distributed agile projects from Tom Stiehm

]]> 707 3 https://cdn.slidesharecdn.com/ss_thumbnails/implementingcloud-baseddevopsfordistributedagileprojects-final-130630201629-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Integrating security into Continuous Delivery /slideshow/integrating-security-into-continuous-delivery-v1/17334870 integratingsecurityintocontinuousdeliveryv1-130318211051-phpapp02
How to integrate application security into an Agile Continuous Delivery framework.]]>
How to integrate application security into an Agile Continuous Delivery framework.]]> Mon, 18 Mar 2013 21:10:51 GMT /slideshow/integrating-security-into-continuous-delivery-v1/17334870 tstiehm@slideshare.net(tstiehm) Integrating security into Continuous Delivery tstiehm How to integrate application security into an Agile Continuous Delivery framework. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/integratingsecurityintocontinuousdeliveryv1-130318211051-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> How to integrate application security into an Agile Continuous Delivery framework.

Integrating security into Continuous Delivery from Tom Stiehm

]]> 5576 5 https://cdn.slidesharecdn.com/ss_thumbnails/integratingsecurityintocontinuousdeliveryv1-130318211051-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 https://cdn.slidesharecdn.com/profile-photo-tstiehm-48x48.jpg?cb=1728393045 Tom has been developing applications and managing software development teams for over twenty years. As CTO of Coveros, he is responsible for the oversight of all technical projects and integrating new technologies and testing practices into software development projects. Recently, Tom has been focusing on how to incorporate DevSecOps and agile best practices into projects and how to achieve a balance between team productivity and cost while mitigating project risks. One of the best risk mitigation techniques Tom has found is leveraging DevSecOps and agile testing practices into all aspects of projects. www/coveros.com https://cdn.slidesharecdn.com/ss_thumbnails/agiledc2024-agilesoftwaredevelopmentantipatterns-241001121524-cb43e222-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/agiledc-2024-agile-software-development-antipatterns-and-how-to-avoid-them/272126658 AgileDC 2024 Agile Sof... https://cdn.slidesharecdn.com/ss_thumbnails/agile2024-agilesoftwaredevelopmentantipatterns-240824201057-e6d2a594-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/agile-software-development-antipatterns-and-how-to-avoid-them/271279124 Agile Software Develop... https://cdn.slidesharecdn.com/ss_thumbnails/shiftingsecurityalldaydevops-191106173518-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/shifting-security-all-day-dev-ops/191104192 Shifting security all ...