Jamie Echlin details how and why to start automating processes and workflows in Atlassian JIRA. Presented at the iDalko event in Antwerp on April 14th 2016.
Designing Self-maintaining UI Tests for Web ApplicationsTechWell
This document discusses the challenges of test automation and proposes some solutions. It notes that products are constantly changing, developers do not always communicate changes, and testers spend significant time fixing broken tests rather than writing new ones. It proposes moving testing earlier in the process, embedding testers with developers, and using automation to prevent broken builds. Moving to more automated and maintainable tests over time can reduce maintenance costs and give testers a better understanding of how software is developed. Key steps include treating test automation as software development, improving presentation layer consistency, and better communication between testers and developers.
Optimizing WordPress - State of Search 2014Brian LaFrance
WordPress is one of the most popular and reliable platforms for publishing content. If your site is running WordPress, there’s a good chance it could be improved with a few simple changes. Learn how to make your WordPress sites faster, more secure, and better for today’s search engine guidelines.
Continuous Deployment involves shipping code as frequently as possible, even multiple times per day. It allows for smaller changes with less risk, faster feedback, and a competitive advantage. To achieve this, companies optimize their deployment process, automate testing and deployments, and measure everything to learn and improve continuously. This approach is enabled by technologies like cloud computing and embraced by companies like Google, Amazon, and Facebook.
This document discusses how organizations can prepare for disasters by making failures routine through practices like chaos engineering and active monitoring. It recommends:
1) Practicing failure scenarios as a team to improve disaster response procedures and checklists.
2) Introducing variables like server crashes and network issues in production environments using chaos engineering to test resiliency.
3) Monitoring application health over time to detect performance trends that could indicate future issues.
4) Treating failures as routine events by having established procedures and checklists to minimize panic and focus response efforts.
A Whole Team Approach to Quality in Continuous Delivery - Lisa CrispinEqual Experts
Watch the video at https://www.equalexperts.com/expert-talks/a-whole-team-approach-to-quality-in-continuous-delivery/
It’s not uncommon for teams practicing, or moving towards, continuous delivery to face a growing backlog of customer-reported bugs and struggle to maintain their deployment cadence. If a team has testers, the testers may be expected to continue with their same testing activities, without any thought as to how those can be fit into CD. Teams without testing specialists often struggle with insufficient coverage from their automated regression tests, and they may miss serious problems entirely because of inadequate exploratory testing.
How can teams build confidence to release small changes so frequently? It’s not just about testing, it’s about finding ways to build quality into the product. This interactive session will introduce:
• a pipeline visualization exercise teams can do to find ways to fit in all testing activities, including manual ones, and shorten feedback loops
• using a test suite canvas to determine the minimum automated tests needed
• ways testing specialists help teams prevent defects and transfer testing skills across the team
This is a session for everyone on the software delivery team, who may or may not have experience with continuous delivery and deployment.
SPEAKER:
Lisa Crispin
Lisa Crispin is the co-author, with Janet Gregory, of three books: Agile Testing
Condensed: A Brief Introduction, More Agile Testing: Learning Journeys for the Whole Team, Agile Testing: A Practical Guide for Testers and Agile Teams; the LiveLessons Agile Testing Essentials video course, and “The Whole Team Approach to Agile Testing” 3-day training course offered through the Agile Testing Fellowship.
Lisa was voted by her peers as the Most Influential Agile Testing Professional Person at Agile Testing Days in 2012. She is co-founder with Janet of Agile Testing Fellowship, Inc.
Please visit www.lisacrispin.com, www.agiletestingfellow.com, and www.agiletester.ca for more.
Lisa is currently a Fellow Quality Owner at OutSystems, helping with the observability practice.
Kanban is a lean methodology for managing workflow. Its core practices include visualizing workflow using a kanban board with columns for different states, limiting work-in-progress to avoid bottlenecks, making policies explicit, and implementing feedback loops to continuously improve. Kanban focuses on managing flow rather than fixed processes, and emphasizes finishing work rather than starting new work. Kanban stand-ups differ from Scrum in that the focus is on identifying impediments rather than commitments.
This document discusses the benefits of continuous deployment including single ownership over projects from conception to deployment, no arbitrary choke points or delays, faster iteration and learning, and empowering developers. It also outlines how to implement continuous deployment using Kanban via Trello for workflow management, Jenkins for continuous integration, and a publicly visible auto-updating change log.
This document provides an agenda for a presentation on automating IT infrastructure with Puppet Enterprise. The presentation will include an introduction, a demo of Puppet Enterprise, and a Q&A session. It promotes Puppet Enterprise as a way to automate provisioning, configuration, and management of machines and applications to deploy code more frequently and with fewer failures, helping businesses meet demands faster.
Designing Self-maintaining UI Tests for Web ApplicationsTechWell
This document discusses the challenges of test automation and proposes some solutions. It notes that products are constantly changing, developers do not always communicate changes, and testers spend significant time fixing broken tests rather than writing new ones. It proposes moving testing earlier in the process, embedding testers with developers, and using automation to prevent broken builds. Moving to more automated and maintainable tests over time can reduce maintenance costs and give testers a better understanding of how software is developed. Key steps include treating test automation as software development, improving presentation layer consistency, and better communication between testers and developers.
Optimizing WordPress - State of Search 2014Brian LaFrance
WordPress is one of the most popular and reliable platforms for publishing content. If your site is running WordPress, there’s a good chance it could be improved with a few simple changes. Learn how to make your WordPress sites faster, more secure, and better for today’s search engine guidelines.
Continuous Deployment involves shipping code as frequently as possible, even multiple times per day. It allows for smaller changes with less risk, faster feedback, and a competitive advantage. To achieve this, companies optimize their deployment process, automate testing and deployments, and measure everything to learn and improve continuously. This approach is enabled by technologies like cloud computing and embraced by companies like Google, Amazon, and Facebook.
This document discusses how organizations can prepare for disasters by making failures routine through practices like chaos engineering and active monitoring. It recommends:
1) Practicing failure scenarios as a team to improve disaster response procedures and checklists.
2) Introducing variables like server crashes and network issues in production environments using chaos engineering to test resiliency.
3) Monitoring application health over time to detect performance trends that could indicate future issues.
4) Treating failures as routine events by having established procedures and checklists to minimize panic and focus response efforts.
A Whole Team Approach to Quality in Continuous Delivery - Lisa CrispinEqual Experts
Watch the video at https://www.equalexperts.com/expert-talks/a-whole-team-approach-to-quality-in-continuous-delivery/
It’s not uncommon for teams practicing, or moving towards, continuous delivery to face a growing backlog of customer-reported bugs and struggle to maintain their deployment cadence. If a team has testers, the testers may be expected to continue with their same testing activities, without any thought as to how those can be fit into CD. Teams without testing specialists often struggle with insufficient coverage from their automated regression tests, and they may miss serious problems entirely because of inadequate exploratory testing.
How can teams build confidence to release small changes so frequently? It’s not just about testing, it’s about finding ways to build quality into the product. This interactive session will introduce:
• a pipeline visualization exercise teams can do to find ways to fit in all testing activities, including manual ones, and shorten feedback loops
• using a test suite canvas to determine the minimum automated tests needed
• ways testing specialists help teams prevent defects and transfer testing skills across the team
This is a session for everyone on the software delivery team, who may or may not have experience with continuous delivery and deployment.
SPEAKER:
Lisa Crispin
Lisa Crispin is the co-author, with Janet Gregory, of three books: Agile Testing
Condensed: A Brief Introduction, More Agile Testing: Learning Journeys for the Whole Team, Agile Testing: A Practical Guide for Testers and Agile Teams; the LiveLessons Agile Testing Essentials video course, and “The Whole Team Approach to Agile Testing” 3-day training course offered through the Agile Testing Fellowship.
Lisa was voted by her peers as the Most Influential Agile Testing Professional Person at Agile Testing Days in 2012. She is co-founder with Janet of Agile Testing Fellowship, Inc.
Please visit www.lisacrispin.com, www.agiletestingfellow.com, and www.agiletester.ca for more.
Lisa is currently a Fellow Quality Owner at OutSystems, helping with the observability practice.
Kanban is a lean methodology for managing workflow. Its core practices include visualizing workflow using a kanban board with columns for different states, limiting work-in-progress to avoid bottlenecks, making policies explicit, and implementing feedback loops to continuously improve. Kanban focuses on managing flow rather than fixed processes, and emphasizes finishing work rather than starting new work. Kanban stand-ups differ from Scrum in that the focus is on identifying impediments rather than commitments.
This document discusses the benefits of continuous deployment including single ownership over projects from conception to deployment, no arbitrary choke points or delays, faster iteration and learning, and empowering developers. It also outlines how to implement continuous deployment using Kanban via Trello for workflow management, Jenkins for continuous integration, and a publicly visible auto-updating change log.
This document provides an agenda for a presentation on automating IT infrastructure with Puppet Enterprise. The presentation will include an introduction, a demo of Puppet Enterprise, and a Q&A session. It promotes Puppet Enterprise as a way to automate provisioning, configuration, and management of machines and applications to deploy code more frequently and with fewer failures, helping businesses meet demands faster.
Lesley Wallace presents on challenges with testing within a Scrum sprint and provides solutions. She asks the audience questions about their testing practices. Wallace explains that everyone on the team is responsible for quality and testing. To test within a sprint, stories must have decreased scope and testing must only focus on the story's scope. If more time is needed for regression testing, a "hardening sprint" can be added before release. Automation helps with testing and there are tools for all budgets.
The document discusses the need for a new cloud team that brings together developers and operations staff. It notes that currently developers and IT have different needs that are not being met, leading to conflicts. When developers deploy applications on their own, many issues can arise around scalability, backups, security and other operational concerns. The document advocates for bringing developers and operations staff together early in the process through a platform team focused on automating deployments, ensuring high availability and scalability, implementing monitoring, and adopting a DevOps approach and culture.
10 Deploys a Day - A Case Study of Continuous Delivery at EnvatoJohn Viner
A presentation to the BankWest Solution Delivery team and the Perth DevOps Meetup describing the delivery processes at Envato that enable us to deploy 10 times a day.
Is it really possible to have your code deployed to production in under in 10 minutes? The ultimate goal of every developer should be to deploy his/her code to production. The sooner your end users will be able to use your feature, the sooner the true business value of the feature kicks in. In this #Devops tale ‘Faster to master without disaster’ Pat Hermens and Pepijn Sitter will take you on a journey on how to achieve this without losing sanity. They each work in very different environments and offer you practical insights into the choices they made in order to help their teams succeed at delivering their software.
The document discusses continuous delivery (CD), which is a strategy for frequently releasing software changes by making the deployment process automated and ensuring the mainline code is always in a deployable state. It outlines some issues with traditional release processes like long release cycles and merge conflicts. CD aims to reduce risks by deploying changes frequently after automated testing. Benefits include being more responsive to demands and reducing pressure and waste. The core benefit is allowing teams to release changes fast while maintaining confidence. It addresses common objections to CD and argues that it is actually a risk reduction strategy.
This document discusses DevOps and the importance of balancing developer and operations mindsets. While tools and automation help enable rapid development cycles, it is also important to not neglect operations concerns like disaster recovery planning, infrastructure capacity planning, and root cause analysis of incidents. True DevOps requires bringing together both developer and operations cultures to respect each other's skills and mindsets. An imbalance, where development is prioritized over operations, can lead to problems as a business scales. Embracing DevOps means using automation to enable change, while still planning for and managing risk with an operations mindset.
This document discusses Agile practices, software development lifecycles (SDLC), and the use of Node.js at PayPal. It outlines typical Agile processes like sprint planning, backlog grooming, pair programming, mob programming, and retrospectives. It also describes PayPal's SDLC pipeline and use of Git flow for source control. Finally, it summarizes how PayPal adopted Node.js in 2012 and has since open sourced frameworks like Kraken.js and tools like Nemo.js while growing a large community of Node.js developers.
This document provides an agenda for an introduction to Puppet Enterprise for automation. The agenda includes why automation is important, a demo of Puppet Enterprise, and a Q&A session. Puppet Enterprise is an automation tool created by Puppet Labs that has over 1000 enterprise customers and allows organizations to deploy code 30x more frequently with 60x fewer failures.
This document discusses a design pattern called the Facade Pattern. It summarizes that the Facade Pattern encapsulates complex systems and provides a simpler interface. It gives an example where a facade pattern is used to handle a credit card transaction in a standardized way without changing existing code. It then discusses how the Strategy Pattern could be used to support different payment types like debit cards or PayPal by deciding the payment algorithm at runtime. The document ends with announcing the next episode will be an open Q&A.
Jira and Confluence - How the company behind those products works - Anatoli K...Dominic Trần
The document introduces Anatoli Kazatchkov, a Confluence development manager at Atlassian with 11 years of software development experience. It then summarizes several Atlassian products like JIRA, Confluence, Bamboo, FishEye & Crucible, and Stash. The document discusses when each product would be used and also covers development roles, problem roles, customer roles, and tips for getting software out the door like tracking issues, using version control, writing automated tests, and releasing often.
OOP 2016 - Faster releases and simpler operationsRoman Spitzbart
This document discusses how Dynatrace helps enable faster software releases while maintaining quality. It promotes Dynatrace's application performance monitoring and unified endpoint management capabilities. Dynatrace analyzes test results, provides metrics for each test, and detects regressions based on measurements to help ensure quality gates are passed during continuous integration/delivery pipelines. The document also briefly describes Dynatrace's full stack monitoring from the browser to infrastructure using a single agent for auto-discovery, modeling, and analytics.
Introduction to Puppet Enterprise 03-31-2016Puppet
This document provides an introduction and agenda for a presentation on Puppet Enterprise for automating IT infrastructure. The presentation will demonstrate how Puppet Enterprise can help organizations automate provisioning, configuration, and management of servers and applications to deploy code more frequently and reduce failures, allowing teams to meet business demands faster and more reliably. The agenda includes discussing why automation is needed and common challenges, a demo of Puppet Enterprise, and a Q&A.
Building an Open Source AppSec PipelineMatt Tesauro
Take the concepts of DevOps and apply them to AppSec and you have an AppSec Pipeline. Allow automation, orchestration and some ChatOps to expand the flow of your AppSec team since its not likely to get any bigger.
A software, undergoes countless brainstorm sessions, rigorous testing in IT environment management and then comes to the production. The task of adding more features to software is like a maze game. The end question that leaves everybody wondering is “How the hell did this functionality come here?”. Famous by various other terms like, “Scope creep”, “requirement creep”, refers to unforeseen requests for the addition of features that are not listed in the project scope.
How to Maintain Traceability - While Using JiraPerforce
Jira and traceability are at odds.
Your developers work in Jira to manage tasks and issues. But you need to create a traceability matrix for regulatory compliance — or simply to prove you’ve met requirements and run tests.
So, you’re stuck.
Your developers want to keep using Jira. But it’s a pain to establish that traceability while using Jira. You’d need to track down requirements and tests that are probably maintained in another tool. You’d need to link those requirements and tests to Jira issues and tasks. And you’d need to manually maintain a traceability matrix.
Luckily, there’s an easier way. Join us to learn how.
You’ll find out:
-Why Jira and traceability clash.
-How to bridge the gap between Jira and traceability.
-What Helix ALM can do to make your life easier.
Plus, you’ll see a live demonstration of creating traceability in Helix ALM — while keeping your developers happy in Jira.
This document provides tips for improving email communication and reducing unnecessary emails. It suggests strengthening email subjects using an Action, Summary, Background, Close format. Emails should be kept concise by chunking key points, eliminating attachments, and adding next steps. Reply-All and carbon copy should be used appropriately as they can lead to more emails. Sending fewer, more targeted emails that are timely, relevant, complete, compliant and professional will improve communication.
The document discusses Ext JS 4.0 MVC and provides an overview of its key concepts and components. The motivations for using MVC include creating clean, maintainable code that is easier to learn, leverage tooling for, and collaborate on. It then covers the basic components of MVC - views, models, stores, and controllers. Views should be balanced to avoid having too many or too few. Models represent types of data, stores manage that data, and controllers tie everything together by figuring out responsibilities, setting references, and listening to events.
The Anatomy of Continuous Deployment at Scale - 100 deploys a week at Envato ...John Viner
The Envato market development team runs a two sided marketplace platform that powers sites such as themeforest.net and graphicriver.net. This presentation describes how they deploy the application up to 25 times a day while serving up to 200 million requests a week.
Pattern Language for Team Productivity - Mr. Khoa Le & Mr. Thong NguyenScrum Breakfast Vietnam
Recent surveys show that 42% of Agile projects are successful (this is three times better than traditional projects), but 49% of Agile projects are late or over budget, and 9% are even total failures.
Some questions raising:
• Are the Scrum teams in those projects productive?
• Is there any better way to help Scrum teams guarantee the success at the highest effectiveness?
On this presentation, we will answer those questions by sharing a comprehensive set of process improvement patterns that will help all Scrum Teams get significantly faster through showing them how to solve problems in a specific context.
The document discusses build and release management processes at AMD that utilize JIRA for issue tracking, SVN for version control, and Bamboo for continuous integration and deployment. It outlines the JIRA and Bamboo workflow for releasing software across multiple sites, including how build automation scripts are triggered by JIRA transitions to build, test, and deploy code. Examples are provided of a more complex Bamboo pipeline that leverages stages, as well as details on the Python-based framework used to automate the build process.
ABUG 12 - Automate your on- and offboarding like a proJoachim Bollen
All onboarding and offboarding at CalmWare follows standardized processes managed in JIRA. Workflows in JIRA are used to automatically create tasks for recruitment/onboarding and user account requests, and tasks close automatically once completed. A variety of plugins like Adaptavist ScriptRunner and JIRA Automation Plugin are used to automate common actions within the onboarding and offboarding workflows.
Lesley Wallace presents on challenges with testing within a Scrum sprint and provides solutions. She asks the audience questions about their testing practices. Wallace explains that everyone on the team is responsible for quality and testing. To test within a sprint, stories must have decreased scope and testing must only focus on the story's scope. If more time is needed for regression testing, a "hardening sprint" can be added before release. Automation helps with testing and there are tools for all budgets.
The document discusses the need for a new cloud team that brings together developers and operations staff. It notes that currently developers and IT have different needs that are not being met, leading to conflicts. When developers deploy applications on their own, many issues can arise around scalability, backups, security and other operational concerns. The document advocates for bringing developers and operations staff together early in the process through a platform team focused on automating deployments, ensuring high availability and scalability, implementing monitoring, and adopting a DevOps approach and culture.
10 Deploys a Day - A Case Study of Continuous Delivery at EnvatoJohn Viner
A presentation to the BankWest Solution Delivery team and the Perth DevOps Meetup describing the delivery processes at Envato that enable us to deploy 10 times a day.
Is it really possible to have your code deployed to production in under in 10 minutes? The ultimate goal of every developer should be to deploy his/her code to production. The sooner your end users will be able to use your feature, the sooner the true business value of the feature kicks in. In this #Devops tale ‘Faster to master without disaster’ Pat Hermens and Pepijn Sitter will take you on a journey on how to achieve this without losing sanity. They each work in very different environments and offer you practical insights into the choices they made in order to help their teams succeed at delivering their software.
The document discusses continuous delivery (CD), which is a strategy for frequently releasing software changes by making the deployment process automated and ensuring the mainline code is always in a deployable state. It outlines some issues with traditional release processes like long release cycles and merge conflicts. CD aims to reduce risks by deploying changes frequently after automated testing. Benefits include being more responsive to demands and reducing pressure and waste. The core benefit is allowing teams to release changes fast while maintaining confidence. It addresses common objections to CD and argues that it is actually a risk reduction strategy.
This document discusses DevOps and the importance of balancing developer and operations mindsets. While tools and automation help enable rapid development cycles, it is also important to not neglect operations concerns like disaster recovery planning, infrastructure capacity planning, and root cause analysis of incidents. True DevOps requires bringing together both developer and operations cultures to respect each other's skills and mindsets. An imbalance, where development is prioritized over operations, can lead to problems as a business scales. Embracing DevOps means using automation to enable change, while still planning for and managing risk with an operations mindset.
This document discusses Agile practices, software development lifecycles (SDLC), and the use of Node.js at PayPal. It outlines typical Agile processes like sprint planning, backlog grooming, pair programming, mob programming, and retrospectives. It also describes PayPal's SDLC pipeline and use of Git flow for source control. Finally, it summarizes how PayPal adopted Node.js in 2012 and has since open sourced frameworks like Kraken.js and tools like Nemo.js while growing a large community of Node.js developers.
This document provides an agenda for an introduction to Puppet Enterprise for automation. The agenda includes why automation is important, a demo of Puppet Enterprise, and a Q&A session. Puppet Enterprise is an automation tool created by Puppet Labs that has over 1000 enterprise customers and allows organizations to deploy code 30x more frequently with 60x fewer failures.
This document discusses a design pattern called the Facade Pattern. It summarizes that the Facade Pattern encapsulates complex systems and provides a simpler interface. It gives an example where a facade pattern is used to handle a credit card transaction in a standardized way without changing existing code. It then discusses how the Strategy Pattern could be used to support different payment types like debit cards or PayPal by deciding the payment algorithm at runtime. The document ends with announcing the next episode will be an open Q&A.
Jira and Confluence - How the company behind those products works - Anatoli K...Dominic Trần
The document introduces Anatoli Kazatchkov, a Confluence development manager at Atlassian with 11 years of software development experience. It then summarizes several Atlassian products like JIRA, Confluence, Bamboo, FishEye & Crucible, and Stash. The document discusses when each product would be used and also covers development roles, problem roles, customer roles, and tips for getting software out the door like tracking issues, using version control, writing automated tests, and releasing often.
OOP 2016 - Faster releases and simpler operationsRoman Spitzbart
This document discusses how Dynatrace helps enable faster software releases while maintaining quality. It promotes Dynatrace's application performance monitoring and unified endpoint management capabilities. Dynatrace analyzes test results, provides metrics for each test, and detects regressions based on measurements to help ensure quality gates are passed during continuous integration/delivery pipelines. The document also briefly describes Dynatrace's full stack monitoring from the browser to infrastructure using a single agent for auto-discovery, modeling, and analytics.
Introduction to Puppet Enterprise 03-31-2016Puppet
This document provides an introduction and agenda for a presentation on Puppet Enterprise for automating IT infrastructure. The presentation will demonstrate how Puppet Enterprise can help organizations automate provisioning, configuration, and management of servers and applications to deploy code more frequently and reduce failures, allowing teams to meet business demands faster and more reliably. The agenda includes discussing why automation is needed and common challenges, a demo of Puppet Enterprise, and a Q&A.
Building an Open Source AppSec PipelineMatt Tesauro
Take the concepts of DevOps and apply them to AppSec and you have an AppSec Pipeline. Allow automation, orchestration and some ChatOps to expand the flow of your AppSec team since its not likely to get any bigger.
A software, undergoes countless brainstorm sessions, rigorous testing in IT environment management and then comes to the production. The task of adding more features to software is like a maze game. The end question that leaves everybody wondering is “How the hell did this functionality come here?”. Famous by various other terms like, “Scope creep”, “requirement creep”, refers to unforeseen requests for the addition of features that are not listed in the project scope.
How to Maintain Traceability - While Using JiraPerforce
Jira and traceability are at odds.
Your developers work in Jira to manage tasks and issues. But you need to create a traceability matrix for regulatory compliance — or simply to prove you’ve met requirements and run tests.
So, you’re stuck.
Your developers want to keep using Jira. But it’s a pain to establish that traceability while using Jira. You’d need to track down requirements and tests that are probably maintained in another tool. You’d need to link those requirements and tests to Jira issues and tasks. And you’d need to manually maintain a traceability matrix.
Luckily, there’s an easier way. Join us to learn how.
You’ll find out:
-Why Jira and traceability clash.
-How to bridge the gap between Jira and traceability.
-What Helix ALM can do to make your life easier.
Plus, you’ll see a live demonstration of creating traceability in Helix ALM — while keeping your developers happy in Jira.
This document provides tips for improving email communication and reducing unnecessary emails. It suggests strengthening email subjects using an Action, Summary, Background, Close format. Emails should be kept concise by chunking key points, eliminating attachments, and adding next steps. Reply-All and carbon copy should be used appropriately as they can lead to more emails. Sending fewer, more targeted emails that are timely, relevant, complete, compliant and professional will improve communication.
The document discusses Ext JS 4.0 MVC and provides an overview of its key concepts and components. The motivations for using MVC include creating clean, maintainable code that is easier to learn, leverage tooling for, and collaborate on. It then covers the basic components of MVC - views, models, stores, and controllers. Views should be balanced to avoid having too many or too few. Models represent types of data, stores manage that data, and controllers tie everything together by figuring out responsibilities, setting references, and listening to events.
The Anatomy of Continuous Deployment at Scale - 100 deploys a week at Envato ...John Viner
The Envato market development team runs a two sided marketplace platform that powers sites such as themeforest.net and graphicriver.net. This presentation describes how they deploy the application up to 25 times a day while serving up to 200 million requests a week.
Pattern Language for Team Productivity - Mr. Khoa Le & Mr. Thong NguyenScrum Breakfast Vietnam
Recent surveys show that 42% of Agile projects are successful (this is three times better than traditional projects), but 49% of Agile projects are late or over budget, and 9% are even total failures.
Some questions raising:
• Are the Scrum teams in those projects productive?
• Is there any better way to help Scrum teams guarantee the success at the highest effectiveness?
On this presentation, we will answer those questions by sharing a comprehensive set of process improvement patterns that will help all Scrum Teams get significantly faster through showing them how to solve problems in a specific context.
The document discusses build and release management processes at AMD that utilize JIRA for issue tracking, SVN for version control, and Bamboo for continuous integration and deployment. It outlines the JIRA and Bamboo workflow for releasing software across multiple sites, including how build automation scripts are triggered by JIRA transitions to build, test, and deploy code. Examples are provided of a more complex Bamboo pipeline that leverages stages, as well as details on the Python-based framework used to automate the build process.
ABUG 12 - Automate your on- and offboarding like a proJoachim Bollen
All onboarding and offboarding at CalmWare follows standardized processes managed in JIRA. Workflows in JIRA are used to automatically create tasks for recruitment/onboarding and user account requests, and tasks close automatically once completed. A variety of plugins like Adaptavist ScriptRunner and JIRA Automation Plugin are used to automate common actions within the onboarding and offboarding workflows.
MantisBT is an open source web based issue / bug tracking system.This is released under the terms of the GNU General Public License version 2.
This presentation covers the Tracker features for non admin users & the generic work flow of Tracker to use it as a BTS and a Task management System.
Building Atlassian Plugins with Groovy - Atlassian Summit 2010 - Lightning TalksAtlassian
Groovy is a dynamic language that runs on the JVM and provides features like closures, builders, and domain specific languages that make developing Atlassian plugins more productive compared to Java. Groovy code is more concise and readable than equivalent Java code for many tasks like iterating over lists and parsing XML. Dynamic typing in Groovy does not preclude robust IDE support and tooling. Groovy can leverage Java libraries and is a fully-featured language suitable for professional development.
Auditing Your Build and Release Infrastructure - Atlassian Summit 2010 - Ligh...Atlassian
The document discusses auditing your build and release processes. It recommends defining your build process, measuring your infrastructure performance, setting up controlled builds, ensuring sufficient build agent capacity, treating the build as your product, and communicating with relevant stakeholders. The overall goal is to lay the groundwork, quantify metrics, establish controls, allocate resources, take ownership, and gather feedback around your organization's software development builds.
Fast then Faster - a Retrospective on RetrospectivesAtlassian
So, you’re agile. You’ve got a healthy backlog, you understand your team’s velocity, and you’re holding retrospectives. You’re in a good place – right? Maybe not. You may have a handle on the quality of your stories & their output, but what about that of your team and those around you? Or your agile processes themselves?
Retrospectives are a great way to get feedback, but they are often both undervalued and underutilized as a tool for improvement. Agile gets you fast, but retrospectives get you faster.
We’ll walk you through what good and bad retrospectives look like, how to tell when they’re failing, and (more importantly) how to uncover what's lurking behind bias, ego, and protocol.
If you’re in doubt if this session is for you, suggest a team under pressure skips the retrospective this week, and see just how quickly they drop the most important part of the agile cycle!
Products covered:
JIRA Software, Confluence, Bitbucket, Bamboo, Fisheye / Crucible
This document discusses using Docker and Bamboo for continuous integration and deployment pipelines. It provides examples of configuring Bamboo to build, test, and deploy Docker images and applications. It also describes using Docker Compose in Bamboo pipelines and customizing Bamboo virtual machines with Packer and Ansible to have Docker pre-installed.
How Atlassian's Build Engineering Team Has Scaled to 150k Builds Per Month an...Peter Leschev
Peter Leschev presented on how the Build Engineering team at Atlassian scaled their continuous integration infrastructure to handle a massive increase in builds from 21k per month to over 150k per month. Some key things they did were adopting infrastructure as code practices with Puppet, building stateless build agents, monitoring Bamboo servers, and using tools like Packer, Terraform, and self-service portals to improve reliability and developer experience at scale.
A lean automation blueprint for testing in continuous deliverySauce Labs
Testing in Continuous Delivery changes test automation. It demands more automation but also requires immediate feedback. Many test teams today suffer from two extremes. Too little or no automation to organizations with hundreds of thousands of tests constantly running all kinds of VMs takes multiple days to execute. Any hope of Continuous Delivery or Pipeline Automation makes these states unsustainable.
Code Palousa presentation- "Giving Digital Eyes to your Synthetic Tests"Christopher Hamm
My project combines open source technologies of Tensorflow with major computer vision model to create a powerful computer vision API. In the project, it can evaluate confidence levels for each labels using good training data. The practical application example will include the computer vision API integrated with a Selenium test script setup. The end result is a robust visual testing tool that can determine if a page compares better to a working state vs a failing state.
The document discusses agile testing approaches. It defines testing as executing software with test cases to find failures and demonstrate correct execution. It then discusses key aspects of agile testing including: running tests iteratively throughout development rather than just at the end; automating tests wherever practical; and having testers work collaboratively as part of development teams. It outlines success factors like focusing on delivering customer value and continually improving testing practices. The document advocates for automating a large portion of testing to provide rapid feedback and free up resources while balancing automation costs.
Incorporating UX into an Agile MethodologyAmy Powell
The document discusses incorporating user experience (UX) design into an Agile development methodology. It outlines the key parts of Agile like user stories, backlogs, and sprints. It then provides three principles for combining UX and Agile: iterate by making mistakes faster, scale by doing more with less, and simplify by keeping things "good enough." Specific tactics are described like using Sprint Zero to get ahead, prioritizing work, and embracing failures to find solutions. The importance of the UX designer's mindset and role on an Agile team is emphasized.
Pavel Kulagin discussed scaling mobile automation at Badoo. He covered first implementing tests and problems encountered, increasing test amounts while maintaining a proper test pyramid with more integration and unit tests than UI tests. Kulagin emphasized helping rather than obstructing others and calculating time saved. Tips included treating automation code like production, supporting parallelization, smart test runs, documentation and easy setup. Mythbusting dispelled ideas that 100% functionality can be automated or all tests require real devices. The key is decreasing flakiness, increasing speed, and creating an easy to use tool while supporting developers and QA.
This document provides an overview of how Itslearning, an educational software company, implemented Scrum using Jira and Greenhopper. Key points include:
- Itslearning had been using Scrum for years but found it difficult to implement in practice. They switched to using Jira and Greenhopper six months ago.
- Challenges included estimating stories, managing work in Greenhopper, addressing incomplete work or bugs found at the end of sprints.
- Solutions involved managing stories and burn-down charts in Greenhopper, prioritizing bug fixes, and addressing idle team members through training or early start on next sprint's work.
- While Scrum theory proposes completed work can be
Instead of being just another cost center for a customer where you develop what you're told, how can you become proactive by understanding the business requirement and truly being a Quality Enabler? Xian Tharindra shares some great insights on this
The document discusses strategies for software product development that balance speed and quality, including:
1) Focusing on getting a minimum viable product to market quickly through short iterative development cycles rather than extensive planning.
2) Establishing processes like continuous integration, source control, and automated testing to catch defects early and allow fast iteration.
3) Hiring selectively and spreading ownership of the product across a small team to allow flexibility over bureaucracy.
This document discusses running acceptance tests as monitors in production environments. It describes why this can be useful for failure detection, capacity planning, and gaining business insights. However, care must be taken to avoid polluting data or sending unnecessary alerts. The author demonstrates a tool called atam4j that treats acceptance tests as a microservice, similar to other applications, making them easier to deploy and monitor in production.
Splunk'ing JIRA for deep insights into application, database, and server heal...Cprime
Jira is great at storing, associating, and aggregating user-generated data across many dimensions for enablement of, and deep insights into, an organization's project planning and tracking workflow. However, it is not terribly good at providing important and actionable system-generated data about itself. As Jira adoption grows and scales throughout an enterprise, it becomes a business-critical production application that must be performant 24/7. We will discuss many common performance problems that he has experienced over the years as a Jira administrator, which inspired him to explore methods to track and correlate historical performance metrics and to provide actionable and predictive metrics to avoid future problems. We will also present a real-world show-and-tell for how this concept can be implemented with a machine data aggregator like Splunk.
Learn JIRA Quickly
Plan, track, work – smarter and faster
http://www.udemy.com/learn-jira-quickly
Enhance your resume skills and improve your productivity quickly
JIRA is the project management and issue tracking software. It is used by teams in all types of products and industries. It's used by Agile teams, bug tracking, helpdesk tickets and thousands of companies!
It's a must skill to have in today's industry and this course will get you started with JIRA in under 2 hours.
Monitoring Principles
This document summarizes key monitoring principles, including anti-patterns to avoid and design patterns to employ. Anti-patterns discussed include tool obsession, treating monitoring as a separate job, checkbox monitoring without understanding what indicates health, and relying too heavily on monitoring as a crutch rather than fixing underlying issues. Design patterns promoted are having a composable monitoring platform using multiple specialized tools, starting monitoring from the user perspective, leveraging monitoring tools from vendors rather than building custom solutions, and viewing monitoring as an ongoing process of continual improvement. The presentation concludes with time for questions.
Ken Johnston - Big Bugs That Got Away - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on Big Bugs That Got Away by Ken Johnston . See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Mobile User Experience:Auto Drive through Performance MetricsAndreas Grabner
Believe it or not - 85% of mobile apps are removed after first usage! In this presentation - given at the APM Meetup in Singapore in April 2015 - I talked about the challenges, best practices and especially metrics to avoid this situation.
Key Points of the Presentation
The two key trends "Internet of Things" and "DevOps" play a big role in our life when we talk about User Experience and especially mobile user experience. In this presentation I tell you what metrics to use to make sure you deliver your ideas faster to your mobile end users but also ensuring the right quality and user experience so that your users stay loyal and dont delete the mobile app after first usage.
Adopting A Whole Team Approach To QualityBen Carey
A presentation give at Agile Carolinas on some things that I think are needed to build quality software.
The content of the presentation is in the presenter notes.
The Top 5 Skills Enterprise Admins Need to KnowAtlassian
This document outlines 5 key skills that enterprise administrators need to know to manage Atlassian products at scale. The 5 skills are: 1) Governance - centralizing setup, teams, and processes; 2) Performance - understanding factors that impact performance and implementing quick wins; 3) Monitoring - establishing monitoring strategies, metrics, and tools; 4) Upgrade Strategy - deciding on release timing, planning upgrades, and leveraging experts; 5) Human Side of Scaling - empowering users, implementing change control, and providing support. The document provides examples and recommendations for each skill area from Atlassian and Airbnb's experiences scaling their Atlassian instances.
Similar to Automating your processes with JIRA (20)
The APCO Geopolitical Radar - Q3 2024 The Global Operating Environment for Bu...APCO
The Radar reflects input from APCO’s teams located around the world. It distils a host of interconnected events and trends into insights to inform operational and strategic decisions. Issues covered in this edition include:
NIMA2024 | De toegevoegde waarde van DEI en ESG in campagnes | Nathalie Lam |...BBPMedia1
Nathalie zal delen hoe DEI en ESG een fundamentele rol kunnen spelen in je merkstrategie en je de juiste aansluiting kan creëren met je doelgroep. Door middel van voorbeelden en simpele handvatten toont ze hoe dit in jouw organisatie toegepast kan worden.
𝐔𝐧𝐯𝐞𝐢𝐥 𝐭𝐡𝐞 𝐅𝐮𝐭𝐮𝐫𝐞 𝐨𝐟 𝐄𝐧𝐞𝐫𝐠𝐲 𝐄𝐟𝐟𝐢𝐜𝐢𝐞𝐧𝐜𝐲 𝐰𝐢𝐭𝐡 𝐍𝐄𝐖𝐍𝐓𝐈𝐃𝐄’𝐬 𝐋𝐚𝐭𝐞𝐬𝐭 𝐎𝐟𝐟𝐞𝐫𝐢𝐧𝐠𝐬
Explore the details in our newly released product manual, which showcases NEWNTIDE's advanced heat pump technologies. Delve into our energy-efficient and eco-friendly solutions tailored for diverse global markets.
IMPACT Silver is a pure silver zinc producer with over $260 million in revenue since 2008 and a large 100% owned 210km Mexico land package - 2024 catalysts includes new 14% grade zinc Plomosas mine and 20,000m of fully funded exploration drilling.
The Most Inspiring Entrepreneurs to Follow in 2024.pdfthesiliconleaders
In a world where the potential of youth innovation remains vastly untouched, there emerges a guiding light in the form of Norm Goldstein, the Founder and CEO of EduNetwork Partners. His dedication to this cause has earned him recognition as a Congressional Leadership Award recipient.
Discover the Beauty and Functionality of The Expert Remodeling Serviceobriengroupinc04
Unlock your kitchen's true potential with expert remodeling services from O'Brien Group Inc. Transform your space into a functional, modern, and luxurious haven with their experienced professionals. From layout reconfiguration to high-end upgrades, they deliver stunning results tailored to your style and needs. Visit obriengroupinc.com to elevate your kitchen's beauty and functionality today.
Ellen Burstyn: From Detroit Dreamer to Hollywood Legend | CIO Women MagazineCIOWomenMagazine
In this article, we will dive into the extraordinary life of Ellen Burstyn, where the curtains rise on a story that's far more attractive than any script.
[To download this presentation, visit:
https://www.oeconsulting.com.sg/training-presentations]
This presentation is a curated compilation of PowerPoint diagrams and templates designed to illustrate 20 different digital transformation frameworks and models. These frameworks are based on recent industry trends and best practices, ensuring that the content remains relevant and up-to-date.
Key highlights include Microsoft's Digital Transformation Framework, which focuses on driving innovation and efficiency, and McKinsey's Ten Guiding Principles, which provide strategic insights for successful digital transformation. Additionally, Forrester's framework emphasizes enhancing customer experiences and modernizing IT infrastructure, while IDC's MaturityScape helps assess and develop organizational digital maturity. MIT's framework explores cutting-edge strategies for achieving digital success.
These materials are perfect for enhancing your business or classroom presentations, offering visual aids to supplement your insights. Please note that while comprehensive, these slides are intended as supplementary resources and may not be complete for standalone instructional purposes.
Frameworks/Models included:
Microsoft’s Digital Transformation Framework
McKinsey’s Ten Guiding Principles of Digital Transformation
Forrester’s Digital Transformation Framework
IDC’s Digital Transformation MaturityScape
MIT’s Digital Transformation Framework
Gartner’s Digital Transformation Framework
Accenture’s Digital Strategy & Enterprise Frameworks
Deloitte’s Digital Industrial Transformation Framework
Capgemini’s Digital Transformation Framework
PwC’s Digital Transformation Framework
Cisco’s Digital Transformation Framework
Cognizant’s Digital Transformation Framework
DXC Technology’s Digital Transformation Framework
The BCG Strategy Palette
McKinsey’s Digital Transformation Framework
Digital Transformation Compass
Four Levels of Digital Maturity
Design Thinking Framework
Business Model Canvas
Customer Journey Map
Call8328958814 satta matka Kalyan result satta guessing➑➌➋➑➒➎➑➑➊➍
Satta Matka Kalyan Main Mumbai Fastest Results
Satta Matka ❋ Sattamatka ❋ New Mumbai Ratan Satta Matka ❋ Fast Matka ❋ Milan Market ❋ Kalyan Matka Results ❋ Satta Game ❋ Matka Game ❋ Satta Matka ❋ Kalyan Satta Matka ❋ Mumbai Main ❋ Online Matka Results ❋ Satta Matka Tips ❋ Milan Chart ❋ Satta Matka Boss❋ New Star Day ❋ Satta King ❋ Live Satta Matka Results ❋ Satta Matka Company ❋ Indian Matka ❋ Satta Matka 143❋ Kalyan Night Matka..
Unveiling the Dynamic Personalities, Key Dates, and Horoscope Insights: Gemin...my Pandit
Explore the fascinating world of the Gemini Zodiac Sign. Discover the unique personality traits, key dates, and horoscope insights of Gemini individuals. Learn how their sociable, communicative nature and boundless curiosity make them the dynamic explorers of the zodiac. Dive into the duality of the Gemini sign and understand their intellectual and adventurous spirit.
Prescriptive analytics BA4206 Anna University PPTFreelance
Business analysis - Prescriptive analytics Introduction to Prescriptive analytics
Prescriptive Modeling
Non Linear Optimization
Demonstrating Business Performance Improvement
SATTA MATKA DPBOSS KALYAN MATKA RESULTS KALYAN CHART KALYAN MATKA MATKA RESULT KALYAN MATKA TIPS SATTA MATKA MATKA COM MATKA PANA JODI TODAY BATTA SATKA MATKA PATTI JODI NUMBER MATKA RESULTS MATKA CHART MATKA JODI SATTA COM INDIA SATTA MATKA MATKA TIPS MATKA WAPKA ALL MATKA RESULT LIVE ONLINE MATKA RESULT KALYAN MATKA RESULT DPBOSS MATKA 143 MAIN MATKA KALYAN MATKA RESULTS KALYAN CHART
Industrial Tech SW: Category Renewal and CreationChristian Dahlen
Every industrial revolution has created a new set of categories and a new set of players.
Multiple new technologies have emerged, but Samsara and C3.ai are only two companies which have gone public so far.
Manufacturing startups constitute the largest pipeline share of unicorns and IPO candidates in the SF Bay Area, and software startups dominate in Germany.
2. 2
Why customise JIRA?
Because it’s fun
It’s easier than you think
Get more out of JIRA
Be wary of overdoing it
Less is more
Start small, make incremental improvements
3. 3
Are plugins the answer?
• Don’t use any
• No plugin will make your instance:
faster
more stable
more secure
safer
sexier
5. Vanilla JIRA doesn’t do much
So you need plugins
But choose wisely
Public plugins are hard to develop
CI for several versions
Data center...
Fast support
No plugins: Ultra safe
Many plugins: Ultra flexible
6. “One of the plugins
that must be in your
instance - extends
JIRA functionality by
over 9000%”
ScriptRunner Customer Review
The third way…
• Started writing
plugins in 2005
• Authored several
Java plugins
• Got bored and
wrote ScriptRunner
• Almost every
feature exists simply
because I needed it
7. 7
A quick primer
Run JIRA locally, develop locally
Install ScriptRunner or other plugins
Or start writing your own
Test - all paths
Practise - you can't master this overnight
Don't blow up production
Version control your code