DOCSLIB.ORG

Encyclopedia of Agile

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Encyclopedia of Agile Aligning Projects, Enhancing Teams. Encyclopedia of Agile An Indexed glossary of terms used in Agile Software Development Compiled By [email protected] The intention of compiling this Encyclopedia of Agile was to create a document that can be used both as an offline reference, and as an online linked reference to some of the top thought leaders in the software industry. The terms and definitions found in this encyclopedia are public domain. The wording of the definitions were taken from the following sources, with reference links to these sources for more in depth coverage of the terminology definitions and etymology. While the content is not new, or original, I hope that you find the various indexes and references helpful in your search for understanding of all things Agile. http://www.wikipedia.org/ Agile Glossary Agile Glossary Agile Glossary Agile Glossary Scrum.org ScrumAlliance Compiled By [email protected] Scrum Terminology Index Types Of Stories Scrum Roles User ScrumMaster Technical Certified ScrumMaster Defect Product Owner Spike Team Tracer Bullet Delivery Team Research Cross-Functional Team Scrum Activities Planning Release Planning Sprint Planning Backlog Grooming Sprint a.k.a Iteration Daily Scrum a.k.a. Daily Standup Sprint Review a.k.a Demo Retrospective a.k.a Kaizen Scrum Artifacts Backlog Product Backlog Sprint Backlog Burndown Chart Burnup Chart Action Items Parking Lot Product Vision Statement Team Agreements Definition of Done Working Agreements www.cprime.com i Agile Terminology Index * Card-Conversation-Confirmation 2 A 2 Certified ScrumMaster 2 Acceptance Testing 2 Chicken 2 * Adaptive 2 Code Smell 2 * Affinity Estimating 2 Colocation 2 * Agile 2 Continuous Integration 2 Agile Development Practices 2 Cross-Functional Team 2 Agile Estimation 2 * Crystal 2 Agile Manifesto 2 Customer 2 Agile Methods 2 Agile Methodology 2 D 2 Agile Modeling 2 Daily Scrum 2 Agile Planning Basics 2 Daily Standup 2 Agile Project Management 2 Defect 2 Agile Software Development 2 Definition of Done 2 * Agile Unified Process 2 Delivery Team 2 * Agilista 2 * Dependency Injection Principle 2 * Agility 2 Design Pattern 2 Alignment 2 Distributed Development Team 2 ALM 2 Distributed Scrum 2 * Anchoring 2 Domain Model 2 Application Lifecycle Management 2 DSDM 2 * Dynamic Systems Development B 2 Method 2 Backlog 2 Backlog Item 2 E 2 Backlog Item Effort 2 * Earned Value Chart 2 Backlog Grooming 2 Emergence 2 Big Ball of Mud 2 Empiricism 2 Big Visible Charts 2 Epic 2 * Blocked 2 EssUP 2 Bottleneck 2 * Essential Unified Process: 2 Branching 2 Estimation 2 Breaking the Build 2 * Estimate to Complete Chart 2 Build Process 2 Extreme Programming 2 Burn-Down Chart 2 Burn-Up Chart 2 F 2 Business Alignment 2 Fail-Fast 2 Business Value 2 Feature 2 FDD 2 C 2 * Feature Driven Development 2 Capacity 2 Fibonacci Sequence 2 CANI 2 Flow 2 www.cprime.com ii Agile Terminology Index * Forked Development 3 P 3 Fog Of War 3 Pair Programming 3 * Functional Test 3 Parallel Development 3 G 3 * Pareto Principle 3 * Parking Lot 3 H 3 Pattern 3 Performance Test 3 * Ha 3 Pig 3 I 3 Planning 3 Planning Game 3 Impediment 3 Planning Poker 3 INVEST 3 * Pragmatic Programming 3 * Integration Test 3 * Predictive 3 Inspect and Adapt 3 * Prioritization 3 * Interface Segregation Principle 3 * Process Framework 3 * Iron Triangle 3 Product 3 IT Alignment 3 Product Backlog 3 Iteration 3 * Product Backlog Item 3 J 3 Product Owner 3 * Product Roadmap 3 K 3 Product Vision 3 * Productivity 3 Kanban 3 * Profiling 3 * Kata 3 * Kaizen 3 Q 3 L 3 R 3 Lean Software Development 3 * Reactive 3 Levels of Planning, 5 3 Refactoring 3 * Liskov Substitution Principle 3 Release (Software) 3 * Load Test 3 Release Backlog 3 M 3 TBD 3 Minimum Marketable Features 3 Release Management 3 N 3 TBD 3 Release Plan 3 O 3 Release Planning 3 OpenUP 3 Research Story 3 * Open Unified Process 3 * Open Closed Principle 3 TBD 3 * Osmotic Communication 3 Resources 3 TBD 3 www.cprime.com iii Agile Terminology Index Retrospective 4 Test-Driven Development 4 * Ri 4 Time-box 4 * ROI 4 * Tracer Bullet 4 * Ron Dori 4 * Transparency 4 * Tuckman Model 4 S 4 * Schedule 4 U 4 * Scope 4 Unit Testing 4 Scrum 4 User Story 4 ScrumBut 4 ScrummerFall 4 V 4 ScrumPlus 4 Velocity 4 Scrum Team 4 * Velocity Tracking 4 ScrumMaster 4 Vision 4 Scrum Snowman 4 Voice of the Customer (VOC) 4 Self-Organization 4 * Shu 4 W 4 * Shu-Ha-Ri 4 Wiki 4 * Sidebar 4 * WIP 4 * Single Responsibility Principle 4 * Work Breakdown Structure 4 Software Quality Metrics 4 Work in Progress (WIP) 4 * SOLID OOD Principles 4 Spike 4 X 4 Sprint 4 XP 4 Sprint Backlog 4 Sprint Burn-Down Chart 4 Y 4 Sprint Planning Meeting 4 * YAGNI 4 Sprint Review 4 * YAGRI 4 Stakeholder 4 Standup Meeting 4 Z 4 Story 4 Story Points 4 Reference Articles and Papers 4 * Stress Test 4 * Swarming 4 Agile Architectures T 4 Agile Architecture 4 by Chris Sterling @ SolutionsIQ, CST Task 4 by Mickey Phoenix @ SolutionsIQ, CSM Task Board 4 * Task Breakdown 4 Distributed Scrum Team 4 Technical Debt 4 Successful Distributed Agile Team Working * Technical Story 4 Patterns 4 by Monica Yap @ SolutionsIQ, CSM Test Automation 4 www.cprime.com iv Agile Terminology Index Case Study: Implementing Distributed The Price of Uncertainty 5 Extreme Programming 5 by Kevin Thompson @ cPrime.com, CSM, by Monica Yap @ SolutionsIQ, CSM CSP, PMP, PhD Daily Scrums in a Distributed World 5 How Agile should your Project be? 5 by Kevin Thompson @ cPrime.com, CSM, by Kevin Thompson @ cPrime.com, CSM, CSP, PMP, PhD CSP, PMP, PhD Meta-Scrum Integrating Waterfall and Agile Development 5 Establishing and Maintaining Top to by Shayan Alam @ cPrime.com, PMP Bottom Transparency Using Meta- Scrum 5 Rational Unified Process Best Practices 5 by Brent Barton @ SolutionsIQ, CST by Crystal Lee @ cPrime.com, PMP, Agile Adoption Effective Retrospectives 5 by Kendrick Burson @ cPrime.com, CSM, CSPO Introduction to Scrum 5 by Kevin Thompson @ cPrime.com, CSM, CSP, PMP, PhD Transitioning From Time-Based to Relative Estimation 5 Scrum as Project Management 5 by Ilan Goldstein @ ScrumAlliance.org, CSM, by Kevin Thompson @ cPrime.com, CSM, CSPO, CSP CSP, PMP, PhD 5 Common Mistakes We Make Writing User The Agile Story: Scrum Meets PMP 5 Stories 5 by Crystal Lee @ cPrime, PMP, CSM by Krystian Kaczor @ ScrumAlliance; CSM, CSP When to Use Scrum 5 by Kevin Thompson @ cPrime.com, CSM, Agile Project Dashboards 5 CSP, PMP, PhD Bringing value to stakeholders and top management Agile Top-Down: Striking a Balance 5 by Leopoldo Simini @ ScrumAlliance; CSM, by Bryan Stallings @ SolutionsIQ, CST CSP Agile ROI Part I: The Business Case for Daily Stand-up, Beyond Mechanics: A Agility 5 Measure of Self-Organization 5 by John Rudd @ SolutionsIQ by Bachan Anand CSM, CSPO, CSP Agile ROI Part II: The Business Case for Affinity Estimation for Release Planning 5 by Monica Yap @ SolutionsIQ Agility 5 by David Wylie @ SolutionsIQ Managing Risk in Scrum, Part 1 5 by Valerie Morris @ SolutionsIQ Scrum in the Enterprise 5 by Kevin Thompson @ cPrime.com, CSM, CSP, PMP, PhD Product Owner Anti-Patterns 5 by Monica Yap @ SolutionsIQ How Uncertainty Works 5 by Kevin Thompson @ cPrime.com, CSM, Card-Conversation-Confirmation 5 CSP, PMP, PhD by Ron Jeffries, 2001 www.cprime.com v Agile Terminology Index Recognizeing Bottlenecks in Scrum 6 Manager 2.0: The Role of the Manager in by Dhaval Panchal @ SolutionsIQ, CST Scrum 6 by Pete Deemer @ ScrumAlliance; CSM, CSP, If At First You Don't Succeed, Fail, Fail CST Again 6 by Michael Tardiff @ SolutionsIQ, CSM, CSPO What is the Definition of Done (DoD) in Agile? 6 by Dhaval Panchal @ SolutionsIQ, CST How Should We Deal With the Mess That Scrum Exposes? 6 by Monica Yap @ SolutionsIQ, CSM, CSPO The Afternoon ScrumMaster: Keeping Agile Teams on Track 6 by Dhaval Panchal @ SolutionsIQ The Short Short Story 6 by Paul Dupuy @ ScrumAlliance; CSM Is Sustainable Pace Nice to Have? Think Again! 6 by Manoj Vadakkan CSM, CSP Agile User Interface Design and Information Architecture From the Trenches 6 by Robin Dymond @ ScrumAlliance; CSM, CSP, CST Why Agile Does Matter in an Embedded Development Environment 6 by Bent Myllerup @ ScrumAlliance; CSM, CSPO, CSP, CSC The Illusion of Precision 6 by Jim Schiel @ ScrumAlliance; CSM, CSP, CST Specialization and Generalization in Teams6 by Bas Vodde @ ScrumAlliance; CSM, CSPO, CSP, CST The Importance of Self-Organisation 6 by Geoff Watts @ ScrumAlliance; CSM, CSP, CSC, CST www.cprime.com vi Encyclopedia of Agile Terminology A Acceptance Testing Formal testing conducted to determine whether or not a system satisfies its acceptance criteria and to enable the customer to determine whether or not to accept the system. Reference: Wikipedia Return To Glossary * Adaptive Return To Glossary * Affinity Estimating Affinity Estimating is a process to quickly estimate a large number of stories with high level SWAG estimates relative to other stories in the same project. To popular tactics are to estimate using either relative or absolute points. Estimating with absolute units: When estimating with absolute units the facilitator will quickly review several stories, asking the team for a flash vote on size (1,2,3,5,8,13,Epic). each new story is compared to the previously voted stories for equivalent size. Each vote is a flash vote, no more than 60 seconds discussion. As each story is estimated the story card is dropped onto the specified stack. By the end of the exercise al stories have been assigned and absolute story point size Estimating relative units: When estimating with relative units the delivery team works in parallel, each selecting a stack of stories and sorting them on a wall, floor or table in relative size, smallest to largest.
Load more

Recommended publications
  • Meister® Insight Enterprise Development and Lifecycle Challenges
    Meister ® Take Control of Your Build Process ® ® OpenMake Meister enables development teams to control the software build process, providing standardization, acceleration, and auditing. Meister delivers speed, transparency, consistency and repeatability across the soft- ware development lifecycle. Meister saves time and money by shortening development cycles and consolidating time consuming redundant tasks. With Meister, organizations have a simplified process for managing the applica- tion build across diverse languages and platforms. Standardized Build Best Practices Meister is the only solution that gives you complete Meister Build Automation control over the software build. It manages depen- dencies, automatically generates build scripts, exe- cutes accelerated, incremental builds, and provides Build Acceleration detailed audit reports. Meister replaces expensive By directing calculating and managing software de- to maintain homegrown and open source build sys- pendencies, Meister accelerates builds, enabling tems with standardized build services for integrating, teams to implement agile and other fast-moving compilers, linkers, archive tools and other common development processes. Builds are further acceler- development tools into a seamless distributed life- ated by Meister, which can determine which build cycle management system. Teams benefit by imple- tasks can be run in parallel – taking full advan- menting build best practices in a standardized way tage of separate processors on multi-core machine across all languages and platforms. Meister is also hardware. With Meister, agile teams can achieve a programmable environment, so build engineers 10 minute incremental builds for most projects, en- can use the Meister API to develop custom Build suring that continuous integration and unit testing Services that tightly integrate their particular combi- runs smoothly and efficiently for maximum benefit.
    [Show full text]
  • Udeploy® Administration Guide 4.8.5 Udeploy Administration Guide: 4.8.5
    uDeploy® Administration Guide 4.8.5 uDeploy Administration Guide: 4.8.5 Publication date August 2013 Copyright © 2011, 2013 UrbanCode, an IBM Company, Inc. About ............................................................................................................................... 1 Product Documentation ............................................................................................... 1 Product Support ......................................................................................................... 1 Document Conventions ................................................................................................ 1 Documentation notices for IBM uDeploy ................................................................................ 2 Installing and Upgrading Servers and Agents .......................................................................... 5 Installation Recommendations ....................................................................................... 6 System Requirements .................................................................................................. 6 Server Minimum Installation Requirements ............................................................. 6 Recommended Server Installation .......................................................................... 6 Agent Minimum Requirements ............................................................................. 7 32- and 64-bit JVM Support ................................................................................
    [Show full text]
  • Enabling Devops on Premise Or Cloud with Jenkins
    Enabling DevOps on Premise or Cloud with Jenkins Sam Rostam [email protected] Cloud & Enterprise Integration Consultant/Trainer Certified SOA & Cloud Architect Certified Big Data Professional MSc @SFU & PhD Studies – Partial @UBC Topics The Context - Digital Transformation An Agile IT Framework What DevOps bring to Teams? - Disrupting Software Development - Improved Quality, shorten cycles - highly responsive for the business needs What is CI /CD ? Simple Scenario with Jenkins Advanced Jenkins : Plug-ins , APIs & Pipelines Toolchain concept Q/A Digital Transformation – Modernization As stated by a As established enterprises in all industries begin to evolve themselves into the successful Digital Organizations of the future they need to begin with the realization that the road to becoming a Digital Business goes through their IT functions. However, many of these incumbents are saddled with IT that has organizational structures, management models, operational processes, workforces and systems that were built to solve “turn of the century” problems of the past. Many analysts and industry experts have recognized the need for a new model to manage IT in their Businesses and have proposed approaches to understand and manage a hybrid IT environment that includes slower legacy applications and infrastructure in combination with today’s rapidly evolving Digital-first, mobile- first and analytics-enabled applications. http://www.ntti3.com/wp-content/uploads/Agile-IT-v1.3.pdf Digital Transformation requires building an ecosystem • Digital transformation is a strategic approach to IT that treats IT infrastructure and data as a potential product for customers. • Digital transformation requires shifting perspectives and by looking at new ways to use data and data sources and looking at new ways to engage with customers.
    [Show full text]
  • OWASP Presentation Template
    Tips for Building a Successful Application Security Program Reducing Software Risk Denver Chapter January 16, 2013 About Me • Dave Ferguson – Veracode Solutions Architect – Certifications: CISSP, CSSLP • In the Past – Principal Consultant with FishNet Security – Software Applications Developer • Industry Involvement – OWASP • Member, Contributor, Former KC chapter leader • Forgot Password Cheat Sheet – Blog • http://appsecnotes.blogspot.com applications end points network data 4 applications end points $35 billion spent in 2011 network data 5 Solaris iOS ColdFusion Linux ASP.NET JSP PHP Ruby C# C/C++ Java Android Blackberry J2ME Windows Windows VB.net Phone 6 Applications Are Complex Why Is Software a Target? 75% percent of attacks » $300 billion in software take place at the produced or sold each year application layer. 75% » One of the world's largest manufacturing industries 62% of companies experienced security breaches in critical applications within the last year. 62% » No uniform standards or insight into security risk or liability of the final product Upon first test, 8 in 10 58% applications contained XSS 80% and/or SQL injection flaws. 7 "Developers and defenders need to be right every time. An attacker only has to be right once." 8 Big Companies Are Hacked via Web Apps x Source: Verizon Business 2012 Data Breach Investigations Report 9 What kind of application vulnerabilities are out there? 10 Web Apps 11 Source: Veracode State of Software Security Report, Volume 4 Non-Web Apps 12 Source: Veracode State of Software Security Report, Volume 4 Programming Language Breakdown Source: Veracode State of Software Security Report, Volume 4 14 Targeting the Software Supply Chain Lockheed says Cyber Attacks Up Sharply, Suppliers Targeted By Andrea Shalal-Esa | Reuters – Mon, Nov 12, 2012 The Information Security Forum Announces Top Five Security Threats in 2013 Posted November 29, 2012 2.
    [Show full text]
  • Continuous Delivery
    DZONE RESEARCH PRESENTS 2014 GUIDE TO CONTINUOUS DELIVERY BROUGHT TO YOU IN PARTNERSHIP WITH dzone.com/research/continuousdelivery © DZONE, INC. 2014 WELCOME TABLE OF CONTENTS Dear Reader, SUMMARY & HIGHLIGHTS 3 In recent years, we have grown accustomed to a KEY RESEARCH FINDINGS 4 constant stream of information that has fueled our news feeds, flooded our inboxes, and triggered INTRODUCING: CONTINUOUS DELIVERY constant notifications... and in all of the noise, BY STEVE SMITH 6 something has been lost. Clarity, concision, and relevance have become innocent bystanders in an CONTINUOUS DELIVERY PITFALLS age of information overload. While it is true the BY J. PauL REED 10 task of gathering information has become easier, finding the right information, when and where you THE CONTINUOUS DELIVERY need it, has become increasingly complex and, at TOOLCHAIN times, overwhelming. BY MattHEW SKELtoN 14 The guide you hold in your hands (or on your CONTINUOUS DELIVERY VISUALIZED 16 device) is a vital part of DZone’s fight against this growing trend. We recognize that as a technology INFRASTRUCTURE AS CODE: WHEN professional, having actionable knowledge at AUTOMATION ISN’t ENOUGH 22 your fingertips is a necessity. Your business BY MitcH PRONSCHINSKE challenges will not be put on hold while you try to identify the right questions to ask and sort CONTINUOUS DELIVERY MATURITY CHECKLIST 24 through endless information. In publishing our 2014 Guide to Continuous Delivery, we have worked SOLUTION DIRECTORY 25 hard to curate and aggregate a wealth of useful topic knowledge and insight into a concise and informative publication. While this is only our second publication of this CREDITS nature, we have come a long way so far and we have big plans for the future.
    [Show full text]
  • Automated Build Service to Facilitate Continuous Delivery
    MASTER’S THESIS | LUND UNIVERSITY 2015 Automated build service to facilitate Continuous Delivery Ture Karlsson Department of Computer Science Faculty of Engineering LTH ISSN 1650-2884 LU-CS-EX 2015-27 Automated build service to facilitate Continuous Delivery Ture Karlsson [email protected] June 12, 2015 Master’s thesis work carried out at IKEA IT AB. Supervisors: Magnus Glantz, [email protected] Ulf Asklund, [email protected] Examiner: Martin Höst, [email protected] Abstract Continuous delivery can be seen as an evolution from agile software develop- ment methods and high demands to deliver working software quickly. It aims to always be able to deliver working and reliable software in short iterations by continuously integrate, build and test the software. This puts high demands on automation and the focus of this thesis is to automate the pipeline between source code and deployable software artifacts. The problem definition of this thesis is to improve and unify the deployment pipeline of software running on Linux at IKEA IT. The project resulted in a service that supports continuous delivery by providing automated building, testing, signing and deployment of software. It runs in production environment at IKEA IT and provides a high level of automation. It was evaluated with help from end users and the eval- uation showed that the service is useful for the intended users and automate several steps they earlier have had to do manually. Keywords: MSc, build service, continuous delivery, RPM Package Manager, DevOps 2 Acknowledgements I would like to give a big thank you to Magnus Glantz at IKEA IT for all the inspiration and for giving me this opportunity.
    [Show full text]
  • Introducing Continuous Integration in an Enterprise Scale Environment
    UPTEC IT08 014 Examensarbete 30 hp November 2008 Introducing Continuous Integration in an Enterprise Scale Environment Staffan Persson This page intentionally left blank. Abstract Introducing Continuous Integration in an Enterprise Scale Environment Staffan Persson Teknisk- naturvetenskaplig fakultet UTH-enheten This thesis investigates how continuous integration best should be incorporated into a current development environment in order to acquire a shorter time for the Besöksadress: regression testing feedback loop. The product in target is a high availability enterprise Ångströmlaboratoriet Lägerhyddsvägen 1 scale software product within mobile telecom. It utilizes a large commercial relational Hus 4, Plan 0 database for customer associated data and employs approximately one hundred designers. Postadress: Box 536 751 21 Uppsala A continuous integration system needs automatic database integration, compilation, testing, inspection, deployment, and feedback. Measures that are valuable to the build Telefon: process regardless of build time should be given the highest priorities of 018 – 471 30 03 implementation. Feedback has been developed in the form of Continuous Integration Telefax: Web. The first priority at this stage is to introduce unit testing of the database which 018 – 471 30 00 also has to be automatically built whenever updated or changed. Hemsida: The amount of time used to integrate should be as close to ten minutes as possible. http://www.teknat.uu.se/student This goal is reachable if the build process is split into at least two integrations by differentiating unit tests from component tests and, if the software’s functionally divided parts are built separately on local integration servers. Starting integrations automatically could potentially allow broken source code to reside in the source code repository.
    [Show full text]
  • Deployment Automation User's Guide Copyright © 2011-2020 Micro Focus Or One of Its Affiliates
    Deployment Automation User's Guide Copyright © 2011-2020 Micro Focus or one of its affiliates. All rights reserved. The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Contains Confidential Information. Except as specifically indicated otherwise, a valid license is required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Part number: 6.3.1 Publication date: 2020-02-27 2 Deployment Automation Table of Contents Part 1: Introduction .......................................................................................... 19 Chapter 1: Welcome to Deployment Automation ................................................ 21 About This Documentation.............................................................................. 21 Chapter 2: Deployment Automation Overview ................................................... 23 User Interface Overview................................................................................. 24 Examples and the Community .......................................................................
    [Show full text]
  • IBM Udeploy® User Guide 5.0.0 IBM Udeploy User Guide: 5.0.0
    IBM uDeploy® User Guide 5.0.0 IBM uDeploy User Guide: 5.0.0 Publication date January 2013 Copyright © 2013 UrbanCode, an IBM Company, Inc. UrbanCode, an IBM Company, AnthillPro, IBM uDeploy and any other product or service name or slogan or logo contained in this documentation are trademarks of UrbanCode, an IBM Company and its suppliers or licensors and may not be copied, imitated, or used, in whole or in part, without the prior written permission of UrbanCode, an IBM Company or the applicable trademark holder. Ownership of all such trademarks and the goodwill associated therewith remains with UrbanCode, an IBM Company or the applicable trademark holder. Reference to any products, services, processes, or other information, by trade name, trademark, or otherwise does not constitute or imply endorsement, sponsorship, or recommendation thereof by UrbanCode, an IBM Company. All other marks and logos found in this documentation are the property of their respective owners. For a detailed list of all third party intellectual property mentioned in our product documentation, please visit: http://www.UrbanCode, an IBM Company.com/html/company/legal/ trademarks.html. Document Number: 5.0.0.1u About This Book ................................................................................................................ 1 Product Documentation ............................................................................................... 1 Product Support ........................................................................................................
    [Show full text]
  • Resume Template Is the Copyright of Qwikresume.Com
    CONTACT DETAILS Robert Smith 1737 Marshville Road, Alabama AWS DevOps Engineer (123)-456-7899 [email protected] www.qwikresume.com PERSONAL STATEMENT 8+ Plus years of Build & Release and DevOps Engineer Extensive SKILLS Experience in implementing and making teams adapt to Release/Change Build Tools Ant, Maven, Management Process Experience with Continuous Integration Tools (TFS, Gradle, NANT DevOps Jenkins, Hudson & Team City) Experience with software development Docker, Nagios, Chef, methodologies such as Waterfall, Agile & Scrum. Good Knowledge in bash Puppet, Openstack & (shell) /Perl/Expect and exposure to Jython, Python scripting. Hands-on experience on Build and deployment of SOA applications like Oracle Service AWS Working Knowledge Bus (OSB), Oracle Policy Modeling (OPM) and Oracle Business Process Scripting Languages Management (BPM). Linux Sheel Scripting And Advanced Shell WORK EXPERIENCE Scripting Configuration Management Perforce, AWS DevOps Engineer Subversion, GIT, PVCS ABC Corporation - June 2012 – Present Version Manager, Bit Responsibilities: Bucket CI Tools Jenkins, AntHillPro, Teamcity, . Building and maintaining cloud formation templates, chef cookbooks, Bamboo. Operating and scripts to automate and deploy AWS resources and configuration Systems Windows, Unix, changes. RHEL And Solaris . Integrating subversion into Hudson/Jenkins to automate the code check- Databases Oracle, out process used Hudson/Hudson/Jenkins for automating builds and MySql, MSAccess, SQL automating deployments maintained the shell and Perl scripts for the Server Change automation purposes. Management Remedy, . Integrating Jira with git hub version control maintained and and Service Now. administered Jira and assigned the roles for the users. Updating all the activities in Jira for the application team in order to track the status of the user stories or defects.
    [Show full text]
  • RESUME OF: Chris Macgowan
    RESUME OF: Chris Macgowan Chris Macgowan 952 Linwood Avenue Saint Paul, Minnesota 55105 United States Tel: 612.401.2342 email: [email protected] web: http://www.macgowan.com OBJECTIVE: A challenging position as Software Engineer with an emphasis on Object Technology. SOFTWARE ENGINEERING SKILLS: Strong understanding of the relationships between software design, software development, user interface, product testing, implementation, maintenance, support and the many factors that are involved in developing a complete software solution. Developed various applications running under Windows and Linux/Unix. Applied design methodologies and wrote technical specifications using OOAD artifacts and UML. These applications were developed using Java, C++, STL, C#, .NET, MFC, ATL and COM. Web Technologies include Java, HTML, PHP, jQuery, JavaScript and CSS. Developed, documented and applied automated tests using Java, C#, C/C++, JUnit, PERL, Selenium, Ranorex and WinRunner. Database experience includes MySQL, Oracle, Microsoft SQL Server, DB2/2, Informix and Microsoft Access. Developed firmware and hardware for embedded systems based on 8-bit microprocessors/microcontrollers. Member and/or leader of various software development teams. Helped develop in-company standards for quality processes, design methods, test procedures and product specifications. Coordinated and managed product testing and support. Authored and edited user and technical documentation. EMPLOYMENT EXPERIENCE: Thomson Reuters Legal Contract Software Engineer August 2013 to January 2015 Eagan, Minnesota Member of the Platform Quality Assurance Automation Group (QED), responsible for design, development, testing and implementation of software components to support test automation for various Legal Platform Software Products. Lead a small team that designed, developed and tested the RetroLoad Test Automation Application. The RetroLoad Process was designed to move legacy data from a mainframe system into Oracle databases.
    [Show full text]
  • IBM Udeploy® Administration Guide 5.0.0 IBM Udeploy Administration Guide: 5.0.0
    IBM uDeploy® Administration Guide 5.0.0 IBM uDeploy Administration Guide: 5.0.0 Publication date January 2013 Copyright © 2013 UrbanCode, an IBM Company, Inc. UrbanCode, an IBM Company, AnthillPro, IBM uDeploy and any other product or service name or slogan or logo contained in this documentation are trademarks of UrbanCode, an IBM Company and its suppliers or licensors and may not be copied, imitated, or used, in whole or in part, without the prior written permission of UrbanCode, an IBM Company or the applicable trademark holder. Ownership of all such trademarks and the goodwill associated therewith remains with UrbanCode, an IBM Company or the applicable trademark holder. Reference to any products, services, processes, or other information, by trade name, trademark, or otherwise does not constitute or imply endorsement, sponsorship, or recommendation thereof by UrbanCode, an IBM Company. All other marks and logos found in this documentation are the property of their respective owners. For a detailed list of all third party intellectual property mentioned in our product documentation, please visit: http://www.UrbanCode, an IBM Company.com/html/company/legal/ trademarks.html. Document Number: 5.0.0.1a About This Book ................................................................................................................ 1 Product Documentation ............................................................................................... 1 Product Support ........................................................................................................
    [Show full text]