DOCSLIB.ORG

Agile ALM: Lightweight Tools and Agile Strategies

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Free ebooks ==> www.ebook777.com Lightweight tools and agile strategies MANNING MICHAEL HÜTTERMANN www.ebook777.comwww.it-ebooks.info Free ebooks ==> www.ebook777.com Agile ALM www.it-ebooks.info Free ebooks ==> www.ebook777.com www.ebook777.comwww.it-ebooks.info Free ebooks ==> www.ebook777.com Agile ALM Lightweight tools and Agile strategies MICHAEL HÜTTERMANN MANNING SHELTER ISLAND www.it-ebooks.info Free ebooks ==> www.ebook777.com For online information and ordering of this and other Manning books, please visit www.manning.com. The publisher offers discounts on this book when ordered in quantity. For more information, please contact Special Sales Department Manning Publications Co. 20 Baldwin Road PO Box 261 Shelter Island, NY 11964 Email: [email protected] ©2012 by Manning Publications Co. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in the book, and Manning Publications was aware of a trademark claim, the designations have been printed in initial caps or all caps. Recognizing the importance of preserving what has been written, it is Manning’s policy to have the books we publish printed on acid-free paper, and we exert our best efforts to that end. Recognizing also our responsibility to conserve the resources of our planet, Manning books are printed on paper that is at least 15 percent recycled and processed without elemental chlorine. Technical editor: Robert Aiello Manning Publications Co. Development editor: Sebastian Stirling 20 Baldwin Road Copyeditor: Andy Carroll PO Box 261 Typesetter: Marija Tudor Shelter Island, NY 11964 Cover designer: Marija Tudor ISBN: 9781935182634 Printed in the United States of America 12345678910–MAL–17161514131211 www.ebook777.comwww.it-ebooks.info Free ebooks ==> www.ebook777.com To my wife and kids www.it-ebooks.info Free ebooks ==> www.ebook777.com www.ebook777.comwww.it-ebooks.info Free ebooks ==> www.ebook777.com brief contents PART 1 INTRODUCTION TO AGILE ALM ................................... 1 1 ■ Getting started with Agile ALM 3 2 ■ ALM and Agile strategies 34 PART 2 FUNCTIONAL AGILE ALM........................................... 59 3 ■ Using Scrum for release management 61 4 ■ Task-based development 92 PART 3 INTEGRATION AND RELEASE MANAGEMENT ................ 117 5 ■ Integration and release management 119 6 ■ Creating a productive development environment 170 7 ■ Advanced CI tools and recipes 191 PART 4 OUTSIDE-IN AND BARRIER-FREE DEVELOPMENT .......... 247 8 ■ Requirements and test management 249 9 ■ Collaborative and barrier-free development with Groovy and Scala 297 vii www.it-ebooks.info Free ebooks ==> www.ebook777.com www.ebook777.comwww.it-ebooks.info Free ebooks ==> www.ebook777.com contents preface xv acknowledgments xvii about this book xix about the cover illustration xxv PART 1 INTRODUCTION TO AGILE ALM........................ 1 Getting started with Agile ALM 3 1 1.1 Agile ALM at a glance 5 1.2 Evolution of software engineering: moving to Agile ALM 7 SCM and the first ALM trial balloons 8 ■ The dawn of ALM 13 ■ Becoming Agile: Agile ALM 15 1.3 Building blocks of Agile ALM 17 Stakeholder focus 17 ■ Views on releasing and Agile ALM 19 Service orientation, SaaS, IaaS, PaaS 19 ■ Task-based and outside-in 21 ■ Configuration, customization, and plug-ins 22 ■ The polyglot programming world 23 ■ Open source culture 24 ■ Open technology and standards 25 ■ Automation 26 1.4 Comprehensive Agile ALM with lightweight tooling 26 Toolchains and accidental complexity 27 ■ Agile ALM tools 28 ■ Effective and efficient tooling 29 ix www.it-ebooks.info Free ebooks ==> www.ebook777.com x CONTENTS 1.5 Example use case 30 1.6 Summary 33 ALM and Agile strategies 34 2 2.1 The Agile and project management 36 2.2 Agile strategies 40 Version control and a single coding stream 40 ■ Productive workspaces 42 ■ Continuous integration 43 ■ Component repository 50 ■ Quality, standards, and release cycles 51 2.3 The process pitfall, the illusion of control 53 Effectiveness and efficiency 54 ■ Agile ALM and configuration items 54 ■ Agile ALM as change enabler 57 2.4 Summary 57 PART 2 FUNCTIONAL AGILE ALM ............................... 59 Using Scrum for release management 61 3 3.1 Getting started with Scrum release management 62 3.2 Implementing Scrum release management 68 The release 68 ■ The release duration 70 ■ The release content 72 ■ Progress and size of working units 74 Release commitments 75 ■ Synchronization points 76 Feature teams, component teams, caretakers 78 ■ Delivery slots, frozen zone, and code freeze 79 ■ Staging software 81 Quality gates 83 3.3 Release planning vehicles 84 Release calendar 84 ■ Release screenplay 85 3.4 Supporting strategies with Subversion 86 The one-medium approach 86 ■ Hooks 88 ■ Flow and locking 90 3.5 Summary 91 Task-based development 92 4 4.1 Prerequisites for task-based development 93 Coordinating changes 93 ■ Using changesets 94 Associating changesets with tasks 95 www.ebook777.comwww.it-ebooks.info Free ebooks ==> www.ebook777.com CONTENTS xi 4.2 Our first toolchain—JIRA, FishEye, Bamboo, and Mylyn 97 Managing tasks with JIRA 99 ■ Working on tasks with Eclipse and Mylyn 103 ■ Tracking source changes with FishEye 105 Build view with Bamboo 107 4.3 Trac bug tracking and project management 109 Installing Trac 111 ■ The wiki 113 ■ Timeline and sources 114 ■ Roadmap and tickets 115 4.4 Summary 116 PAET 3 INTEGRATION AND RELEASE MANAGEMENT .... 117 Integration and release management 119 5 5.1 The integration and release management function 120 5.2 Maven feature set 124 POMs and dependencies 125 ■ Inheritance and aggregation 127 ■ Lifecycles, phases, and goals 128 Maven and testing 130 ■ Maven ecosystem 131 5.3 Maven component repositories 132 Managing sources and binaries in conjunction 135 Artifactory’s enterprise component repository 137 ■ Using Subversion to serve a simple Maven repository 145 5.4 Releasing with Maven 150 Creating the branch and preparing the release 152 ■ Creating the release 157 ■ Testing the release 158 ■ Useful Maven plug-ins for releasing 160 ■ Using cryptography with Maven 161 ■ Maven assembly 162 ■ Tooling beyond Maven and outlook 167 5.5 Summary 169 Creating a productive development environment 170 6 6.1 Congruent builds and workspace management 171 Workspace management and the VCS 171 ■ Workspace management and integrating code 172 ■ Workspace management and running tests 173 ■ Workspace management and dependencies 174 ■ Workspace management and bootstrapping the development 177 www.it-ebooks.info Free ebooks ==> www.ebook777.com xii CONTENTS 6.2 Using Mockito to isolate systems 177 Isolation and dependency injection 178 ■ Mocks in test-driven development 180 ■ The flavor of behavior-driven development 182 ■ Other handy features of Mockito 182 Antipatterns 184 6.3 Interfacing application containers with Cargo 185 6.4 Remote builds with TeamCity 187 6.5 Summary 190 Advanced CI tools and recipes 191 7 7.1 Integrating other artifact types: Cobol 193 Preconditions and basic thoughts 194 ■ FTP communication with Ant 195 ■ FTP communication with Java 199 7.2 Integrating other artifact types: .NET 201 Using MSBuild to build .NET projects 202 ■ Using TeamCity to trigger .NET builds 203 7.3 Configure: building (web) apps for multiple environments 207 Multiple artifacts with assemblies 208 ■ Applying different configurations 210 ■ Using a distribution profile and executing the example 212 7.4 Building, auditing, and staging with Jenkins 213 Jenkins and triggering jobs 214 ■ Jenkins dashboard and Jenkins jobs 215 ■ Auditing with Jenkins and Sonar 218 Running build fragments in Jenkins only 225 ■ Injecting build numbers into applications 227 ■ Jenkins, Artifactory, staging, and atomic deployment of Maven artifacts 229 7.5 Using Git and git-svn bridge for feature branch–driven CI 238 Feature branching comes to the rescue 241 ■ The Lone Ranger problem and how the git-svn bridge can fix it 243 7.6 Summary 246 PART 4 OUTSIDE-IN AND BARRIER-FREE DEVELOPMENT 247 Requirements and test management 249 8 8.1 Collaborative tests 251 Data-driven tests 253 ■ Acceptance tests 254 www.ebook777.comwww.it-ebooks.info Free ebooks ==> www.ebook777.com CONTENTS xiii Ubiquitous language 255 ■ Executable specifications 256 Behavior-driven development 256 8.2 Acceptance testing with TestNG, Selenium, XStream, and Excel 259 TestNG and the data-driven approach 259 ■ Data-driven testing with XStream 262 ■ Testing the web UI with Selenium, TestNG, and XStream 264 ■ Data-driven testing with Excel 270 8.3 Acceptance testing with Fit, TestNG, and FEST 272 The application 272 ■ The specification 273 ■ Gluing the tests and processing the document 276 ■ Running tests with Ant 278 ■ Running tests with Maven and adding to a Maven site 280 8.4 BDD in FitNesse with GivWenZen 283 Testing with GivWenZen 285 ■ GivWenZen and Java PropertyEditors 290 ■ Adding further scenarios 293 Creating scenarios 295 8.5 Summary 296 Collaborative and barrier-free development with 9 Groovy and Scala 297 9.1 Agile and polyglot with Groovy 298 Low ceremony and scripting 301 ■ Domain-specific languages 302 ■ Testing with easyb and Spock 303 Groovy Maven ecosystem 305 9.2 BDD with specs2 and Scala 306 Scala/specs2 307 ■ Specs2 forms 313 ■ Scala build ecosystem 315 9.3 Summary 315 index 319 www.it-ebooks.info Free ebooks ==> www.ebook777.com www.ebook777.comwww.it-ebooks.info Free ebooks ==> www.ebook777.com preface Welcome to Agile ALM. This book has three main goals. The first is to describe Agile Application Lifecycle Management (ALM) in practical terms and to provide a plan for rolling out Agile strategies and best-of-breed tools. The second purpose is to explain how to create ALM toolboxes based on standard tools used in advanced, real-world cases.
Recommended publications
  • Test Driven .NET Development with Fitnesse

    Test Driven .NET Development with Fitnesse

    Test Driven .NET Development with FitNesse second edition Gojko Adzic Test Driven .NET Development with FitNesse: second edition Gojko Adzic Copy-editor: Marjory Bisset Cover picture: Brian Samodra Published 2009 Copyright © 2008-2009 Neuri Limited Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where these designations appear in this book, and the publisher was aware of a trademark claim, the designations have been printed with initial capital letters or in all capitals. The author has taken care in the preparation of this book, but makes no expressed or implied warranty of any kind and assumes no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. All rights reserved. This publication is protected by copyright, and permission must be obtained from the publisher prior to any prohibited reproduction, storage in a retrieval system, or transmission in any form or by any means, electronic, mechanical, photocopying, recording, or likewise. For information regarding permissions, write to: Neuri Limited 25 Southampton Buildings London WC2A 1AL United Kingdom You can also contact us by e-mail: [email protected] Register your book online Visit http://gojko.net/fitnesse and register your book online to get free PDF updates and notifications about corrections or future editions of this book. ISBN: 978-0-9556836-2-6 REVISION:2009-12-08 Preface to the second edition ........................................................... vii What's new in this version? ..................................................... vii Training and consultancy ................................................................ ix Acknowledgements ........................................................................
  • 2019 Stateof the Software Supply Chain

    2019 Stateof the Software Supply Chain

    2019 State of the Software Supply Chain The 5th annual report on global open source software development presented by in partnership with supported by Table of Contents Introduction................................................................................. 3 CHAPTER 4: Exemplary Dev Teams .................................26 4.1 The Enterprise Continues to Accelerate ...........................27 Infographic .................................................................................. 4 4.2 Analysis of 12,000 Large Enterprises ................................27 CHAPTER 1: Global Supply of Open Source .................5 4.3 Component Releases Make Up 85% of a Modern Application......................................... 28 1.1 Supply of Open Source is Massive ...........................................6 4.4 Characteristics of Exemplary 1.2 Supply of Open Source is Expanding Rapidly ..................7 Development Teams ................................................................... 29 1.3 Suppliers, Components and Releases ..................................7 4.5 Rewards for Exemplary Development Teams ..............34 CHAPTER 2: Global Demand for Open Source ..........8 CHAPTER 5: The Changing Landscape .......................35 2.1 Accelerating Demand for 5.1 Deming Emphasizes Building Quality In ...........................36 Open Source Libraries .....................................................................9 5.2 Tracing Vulnerable Component Release 2.2 Automated Pipelines and Downloads Across Software Supply Chains
  • Analysis and Prediction of Number of Open Bugs Per Day by Using

    Analysis and Prediction of Number of Open Bugs Per Day by Using

    International Journal of Research and Scientific Innovation (IJRSI) | Volume V, Issue V, May 2018 | ISSN 2321–2705 Analysis and Prediction of Open Bugs Using Machine Learning Algorithms Sachin A S, Dr. Rajashree Shettar Department of Computer Science and Engineering, R V College of Engineering, Mysuru Road, Bengaluru, Karnataka, India. Abstract– There are many fault tracking repositories, some of problem[2]. Atlassian JIRA, Bugzilla, Mantis BT, Trac, them are YouTrack, Bugzilla, MantisBT and Atlassian JIRA. YouTrack etc., are some of the issue tracking systems which Atlassian JIRA repository has been used in this study, as it is are used in the software industries. But most extensively extensively accepted by most of the software companies. This accepted are JIRA and Bugzilla as they provide many features repository contains significant information of many projects. which are helpful for software development like task tracking, Each project has different kinds of issues such as bug(faults) reports, enhancement required to an existing feature, and new issues, bug, features many plugins to integrate with versioning feature of the product and task that needs to be done. This paper systems such as Git, mercury etc., and project management. focuses on analysing the previously raised bug report(history) to Consistently both commercial and open source projects understand the correlation and dependability of the attributes experience many changes to represent new client requirements like number of bugs created per day, their priority, number of days or hours taken to resolve etc., The data is then processed with the consideration of improving existing features, creation into a new format which will comply to machine learning of new features or to fix bugs.
  • Project Management Software March 2019

    Project Management Software March 2019

    PROJECT MANAGEMENT SOFTWARE MARCH 2019 Powered by Methodology CONTENTS 3 Introduction 5 Defining Project Management Software 6 FrontRunners (Small Vendors) 8 FrontRunners (Enterprise Vendors) 10 Runners Up 22 Methodology Basics 2 INTRODUCTION his FrontRunners analysis minimum qualifying score of 3.96 Tis a data-driven assessment for Usability and 3.91 for User identifying products in the Project Recommended, while the Small Management software market that Vendor graphic had a minimum offer the best capability and value qualifying score of 4.55 for Usability for small businesses. For a given and 4.38 for User Recommended. market, products are evaluated and given a score for Usability (x-axis) To be considered for the Project and User Recommended (y-axis). Management FrontRunners, a FrontRunners then plots 10-15 product needed a minimum of 20 products each on a Small Vendor user reviews published within 18 and an Enterprise Vendor graphic, months of the evaluation period. based on vendor business size, per Products needed a minimum user category. rating score of 3.0 for both Usability and User Recommended in both In the Project Management the Small and Enterprise graphics. FrontRunners infographic, the Enterprise Vendor graphic had a 3 INTRODUCTION The minimum score cutoff to be included in the FrontRunners graphic varies by category, depending on the range of scores in each category. No product with a score less than 3.0 in either dimension is included in any FrontRunners graphic. For products included, the Usability and User Recommended scores determine their positions on the FrontRunners graphic. 4 DEFINING PROJECT MANAGEMENT SOFTWARE roject management software and document management, as well Phelps organizations manage as at least one of the following: time and deliver projects on time, on tracking, budgeting, and resource budget and within scope.
  • Acceptance Testing How Cslim and Fitnesse Can Help You Test Your Embedded System

    Acceptance Testing How Cslim and Fitnesse Can Help You Test Your Embedded System

    Acceptance Testing How CSlim and FitNesse Can Help You Test Your Embedded System Doug Bradbury Software Craftsman, 8th Light Tutorial Environment git clone git://github.com/dougbradbury/c_learning.git cd c_learning ./bootstrap.sh or with a live CD: cp -R cslim_agile_package c_clearning cd c_learning git pull ./bootstrap.sh Overview Talk w/ exercises: Acceptance Tests Tutorial: Writing Acceptance tests Tutorial: Fitnesse Tutorial: CSlim Talk: Embedded Systems Integration Bonus Topics Introductions Who are you? Where do you work? What experience do you have with ... embedded systems? acceptance testing? FitNesse and Slim? Objectives As a result of this course you will be able to: Understand the purposes of acceptance testing; Use acceptance tests to define and negotiate scope on embedded systems projects; Integrate a CSlim Server into your embedded systems; Objectives (cont) As a result of this course you will be able to: Add CSlim fixtures to your embedded system; Write Fitnesse tests to drive the execution of CSlim fixtures; Write and maintain suites of tests in a responsible manner. Points on a star How many points does this star have? Star Point Specification Points on a star are counted by the number of exterior points. Points on a star How many points does this star have? By Example 3 5 9 Points on a star Now, how many points does this star have? Robo-draw Pick a partner ... Acceptance Testing Collaboratively producing examples of what a piece of software is supposed to do Unit Tests help you build the code right. Acceptance Tests
  • Measuring Test Data Uniformity in Acceptance Tests for the Fitnesse and Gherkin Notations

    Measuring Test Data Uniformity in Acceptance Tests for the Fitnesse and Gherkin Notations

    Journal of Computer Science Original Research Paper Measuring Test Data Uniformity in Acceptance Tests for the FitNesse and Gherkin Notations Douglas Hiura Longo, Patrícia Vilain and Lucas Pereira da Silva Department of Informatics and Statistics, Federal University of Santa Catarina, Florianópolis, Brazil Article history Abstract: This paper presents two metrics designed to measure the data Received: 23-11-2020 uniformity of acceptance tests in FitNesse and Gherkin notations. The Revised: 24-02-2021 objective is to measure the data uniformity of acceptance tests in order Accepted: 25-02-2021 to identify projects with lots of random and meaningless data. Random data in acceptance tests hinder communication between stakeholders Corresponding Author: Douglas Hiura Longo and increase the volume of glue code. The main contribution of this Department of Informatics and paper is the implementation of the proposed metrics. This paper also Statistics, Federal University of evaluates the uniformity of test data from several FitNesse and Gherkin Santa Catarina, Florianópolis, projects found on GitHub, as a means to verify if the metrics are Brazil applicable. First, the metrics were applied to 18 FitNesse project Email: [email protected] repositories and 18 Gherkin project repositories. The measurements taken from these repositories were used to present cases of irregular and uniform test data. Then, we have compared the notations from FitNesse and Gherkin in terms of projects and features. In terms of projects, no significant difference was observed, that is, FitNesse projects have a level of uniformity similar to Gherkin projects. However, in terms of features and test documents, there was a significant difference.
  • Agile Testing Practices

    Agile Testing Practices

    Agile Testing Practices Megan S. Sumrell Director of Transformation Services Valtech Introductions About us… Now about you… Your name Your company Your role Your experience with Agile or Scrum? Personal Expectations Agenda Introductions Agile Overview Traditional QA Teams Traditional Automation Approaches Role of an Agile Tester Testing Activities Refine Acceptance Criteria TDD Manual / Exploratory Testing Defect Management Documentation Performance Testing Regression Testing Agenda Continued Test Automation on Agile Teams Testing on a Greenfield Project Testing on a Legacy Application Estimation Sessions Sprint Planning Meetings Retrospectives Infrastructure Skills and Titles Closing Agile Overview Agile Manifesto "We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more." Scrum Terms and Definitions User Story: high level requirements Product Backlog: list of prioritized user stories Sprint : one cycle or iteration (usually 2 or 4 weeks in length) Daily Stand-up: 15 minute meeting every day to review status Scrum Master: owns the Scrum process and removes impediments Product Owner: focused on ROI and owns priorities on the backlog Pigs and Chickens Traditional QA Teams How are you organized? When do you get involved in the project? What does your “test phase” look like? What testing challenges do you have? Traditional Test Automation Automation Challenges Cost of tools Hard to learn Can’t find time Maintenance UI dependent Only a few people can run them Traditional Test Pyramid UNIT TESTS Business Rules GUI TESTS Will these strategies work in an Agile environment? Food for Thought…….
  • Enhancing IDE Representation of Changes in Git with Refactorings Information

    Enhancing IDE Representation of Changes in Git with Refactorings Information

    REFACTORINSIGHT: Enhancing IDE Representation of Changes in Git with Refactorings Information Zarina Kurbatova,∗ Vladimir Kovalenko,∗y Ioana Savu,z Bob Brockbernd,z Dan Andreescu,z Matei Anton,z Roman Venediktov,x Elena Tikhomirova,∗ Timofey Bryksin∗x ∗JetBrains Research, yJetBrains N.V., zDelft University of Technology, xHigher School of Economics fzarina.kurbatova, vladimir.kovalenko, elena.tikhomirova, [email protected], fa.i.savu-1, B.J.Brockbernd, D.Andreescu, [email protected], [email protected] Abstract—Inspection of code changes is a time-consuming task However, currently IDEs do not provide much insight into that constitutes a big part of everyday work of software engineers. the semantics of changes, and developers still need to put effort Existing IDEs provide little information about the semantics of into figuring out whether and how the changes influence the code changes within the file editor view. Therefore developers have to track changes across multiple files, which is a hard task behavior of code and whether changes across multiple files are with large codebases. connected to each other. Visualizing information related to the In this paper, we present REFACTORINSIGHT, a plugin for semantics of code changes is a promising way to augment the IntelliJ IDEA that introduces a smart diff for code changes in presentation of changes in an IDE. One way of doing it is Java and Kotlin where refactorings are auto-folded and provided to separate the changes that represent refactorings from such with their description, thus allowing users to focus on changes that modify the code behavior like bug fixes and new features.
  • Jetbrains Upsource Comparison Upsource Is a Powerful Tool for Teams Wish- Key Benefits Ing to Improve Their Code, Projects and Pro- Cesses

    Jetbrains Upsource Comparison Upsource Is a Powerful Tool for Teams Wish- Key Benefits Ing to Improve Their Code, Projects and Pro- Cesses

    JetBrains Upsource Comparison Upsource is a powerful tool for teams wish- Key benefits ing to improve their code, projects and pro- cesses. It serves as a polyglot code review How Upsource Compares to Other Code Review Tools tool, a source of data-driven project ana- lytics, an intelligent repository browser and Accuracy of Comparison a team collaboration center. Upsource boasts in-depth knowledge of Java, PHP, JavaScript, Integration with JetBrains Tools Python, and Kotlin to increase the efcien- cy of code reviews. It continuously analyzes Sales Contacts the repository activity providing a valuable insight into potential design problems and project risks. On top of that Upsource makes team collaboration easy and enjoyable. Key benefits IDE-level code insight to help developers Automated workflow, to minimize manual tasks. Powerful search engine. understand and review code changes more efectively. Smart suggestion of suitable reviewers, revi- IDE plugins that allow developers to partici- sions, etc. based on historical data and intel- pate in code reviews right from their IDEs. Data-driven project analytics highlighting ligent progress tracking. potential design flaws such as hotspots, abandoned files and more. Unified access to all your Git, Mercurial, Secure, and scalable. Perforce or Subversion projects. To learn more about Upsource, please visit our website at jetbrains.com/upsource. How Upsource Compares to Other Code Review Tools JetBrains has extensively researched various As all the products mentioned in the docu- tools to come up with a useful comparison ment are being actively developed and their table. We tried to make it as comprehensive functionality changes on a regular basis, this and neutral as we possibly could.
  • You Need to Know About Working from Home

    You Need to Know About Working from Home

    Everything you need to know about working from home Everything you need to know about working from home - Ebook. 1 Table of contents What is remote work and why most people choose to 01 work from home? 4 Benefits of working from home for 02 employees 6 Benefits of working from home for 03 employers 12 Remote work is here to stay, it’s not 04 a temporary trend 16 Debugging work from 05 home 18 Designing your home 06 work space 22 Art of Staying 07 Productive 26 Motivate 08 yourself! 36 Everything you need to know 2 about working from home - Ebook. How to make yourself known 09 and seen 42 Creating “virtual water cooler” in 10 your work space 48 Switching 11 off 52 Addressing loneliness while 12 working remotely 54 Meditation & 13 mindfulness 58 Global Work From 14 Home Day 62 Everything you need to know about working from home - Ebook. 3 What is remote work and why most people choose 01 to work from home? With continuously improving tech- Coworking spaces, social activities, nology and an ever changing work- and regular outdoor trips for example ing culture, remote work is becoming may not be relevant or recommended increasingly common in companies depending on your location and local around the globe. But now a lot of us are government guidelines. Please take finding ourselves in a situation where what you feel makes sense to you and we have to work from home due to the apply it in the safest way possible. We recent COVID-19 outbreak.
  • Agile Project Management Tools

    Agile Project Management Tools

    BULGARIAN ACADEMY OF SCIENCES CYBERNETICS AND INFORMATION TECHNOLOGIES Volume 19, No 4 Sofia 2019 Print ISSN: 1311-9702; Online ISSN: 1314-4081 DOI: 10.2478/cait-2019-0033 Agile Project Management Tools: A Brief Comprative View Deniz Özkan1,2, Alok Mishra2 1Havelsan, A.Ş., 06510, Mustafa Kemal, Çankaya, Ankara, Turkey 2Department of Software Engineering, Atilim University, Turkey E-mails: [email protected] [email protected] Abstract: Agile methodologies are becoming popular in software development. Managers are required to understand project’s progress and product quality without development documents. During Agile practices of the teams and organizations, Agile project management tools are frequently used. The use of such tools leads to achieving speed and efficiency, affects the quality of the software. The quality of final product is mostly related with to project management. Accordingly, the paper provides brief comparative perspective about the popular project management tools for agile projects. 16 popular Agile project management tools have been presented helping agile developers to plan and manage their tasks in an efficient manner. Taiga, Axosoft, Agielan, Planbox are more appropriate for start-up projects. The most twitted and most appreciated tools are reported as Jira, Trello, and VersionOne. SpiraTeam by Inflectra and Pivotal Tracker are other pricing and popular agile tools, providing flexibility to Agile developers and increase collaboration among team members. Keywords: Agile Methodologies, Agile Project Management Tool, Tools, Software Project Management. 1. Introduction Presently, Agile software development method is becoming popular as it helps organizations to develop software projects faster. Most organizations (71%), mention that by using this methodology, projects are 28% more successful than projects managed with traditional methods [1].
  • Architecting TIBCO Streambase Applications Unit 4 Functional Testing

    Architecting TIBCO Streambase Applications Unit 4 Functional Testing

    Architecting TIBCO StreamBase Applications Unit 4 Functional Testing © Copyright 2000-2014 TIBCO Software Inc. StreamBase Functional Testing Overview • Test Methodology and Tooling • Test Development Tasks • Types of Tests • Tool Overview • Functional Test Areas © Copyright 2000-2014 TIBCO Software Inc. 2 StreamBase Test Methodology and Tooling 3 © Copyright 2000-2013 TIBCO Software Inc. Test Methodology and Tooling Partial list taken from Project Methodology Unit: We Can Help. • by validating/ creating recipes for the application of SB specifics to the general rules • by establishing delivery team discipline around particularly important good practices that often fall by the wayside • by promoting systematic use of lifecycle tool support and integrating into customer SDLC practices and infrastructure © Copyright 2000-2014 TIBCO Software Inc. 4 StreamBase Functional Testing: Tasks 5 © Copyright 2000-2013 TIBCO Software Inc. Functional Testing Tasks • Test Development Tasks – Test Plan – Test Case Specification – Test Development – Test Data Generation • Functional Testing Infrastructure and DevOps Setup and Integration • CI Server Integration and SLAs • Regression Suite Initiation and Frequency, Results Review and Notification © Copyright 2000-2014 TIBCO Software Inc. 6 StreamBase Types of Tests 7 © Copyright 2000-2013 TIBCO Software Inc. Types of Application Testing • Functional Requirements Testing • System Integration Testing • Performance Testing and Tuning • Throughput Metrics • Latency Metric • This is a science; see performance unit © Copyright 2000-2014 TIBCO Software Inc. 8 More Types of Testing – Failover/Failback Testing • Application Server Failure • Inbound Messaging Server(s) Failover/Failure • Outbound Messaging Server(s) Failover/Failure • Persistence (RDBMS) Server Failover/Failure • Network Failure • Storage/Cache Failure – Disaster Recovery Testing – Stress Testing/Burn-in © Copyright 2000-2014 TIBCO Software Inc.