DOCSLIB.ORG

Talmatic CV Stepan Sh. Java 1851

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Talmatic CV Stepan Sh. Java 1851 Stepan Sh. Software Engineer Education Educational establishment Gomel State Machine-Building College, Belarus Graduation year 2012 Diploma profession Software Engineer Degree Specialist Additional Education (Courses) Company EPAM Systems Graduation year 2016 Course SAP Hybris mentoring program Foreign Languages Languag Conversational Technical e Reading Writing Speaking Reading Writing Speaking Upper-Interme Upper-Interme Upper-Interme Upper-Interme English Intermediate Intermediate diate diate diate diate Work Experience Summary IT professional with 7+ years of experience in software development, with special focus on Java for web solutions. Professional Skills SKILLS Experience, Level Last used, year in years Enterprise Solution Platforms Alfresco 3 Intermediate 2015 SAP Hybris Commerce 2 Advanced 2017 Programming Languages JavaScript 7 Intermediate 2019 Java 7 Expert 2019 Programming Technologies Spring (MVC/DI/AOP/Integration/Security) 5 Advanced 2019 Spring Boot 3 Novice 2019 JDBC 7 Advanced 2019 Hibernate 7 Intermediate 2019 REST 5 Advanced 2019 SOAP 1 Intermediate 2015 AJAX 5 Advanced 2019 JQuery 3 Novice 2017 JUnit 3 Advanced 2017 Mockito 4 Advanced 2017 PowerMock 3 Intermediate 2017 JSP 7 Advanced 2019 JSF 2 Intermediate 2015 Freemarker 2 Advanced 2017 JasperReports 1 Advanced 2015 Apache POI 4 Advanced 2017 Apache Lucene 3 Intermediate 2015 Apache SOLR 3 Intermediate 2019 Apache Tika 2 Intermediate 2019 Activiti 3 Intermediate 2015 Application Servers Oracle WebLogic 3 Intermediate 2015 Apache Tomcat 2 Advanced 2019 Database Management Systems Oracle Database 3 Novice 2017 MongoDB 1 Novice 2019 MySQL 2 Intermediate 2019 PostgreSQL 2 Intermediate 2019 Database Tools MySQL Workbench 2 Advanced 2019 pgAdmin 2 Advanced 2019 Oracle SQL Developer 7 Advanced 2021 Source Control Systems SVN 2 Intermediate 2013 Git 3 Advanced 2019 Mercurial 2 Intermediate 2015 Build Tools Maven 5 Advanced 2019 Ant 3 Advanced 2019 Webpack 1 Novice 2019 Code Review Tools GitHub 3 Advanced 2019 Crucible 4 Advanced 2017 IDE IntelliJ IDEA 5 Advanced 2019 Oracle JDeveloper 1 Intermediate 2013 Projects Experience Period From: Nov. 2019 To: November. 2019 Project Role Team Leader, project architect Project http://mytableapps.com Uber-Like service for ordering chef’s service for making dinners for some events. Allowing users to search chef’s and home cooks with appropriate kitchen and order them for making great dinners. Admin panel for service administrators, web site, mobile apps. Participation ● Team coordination ● Planning and estimating development process ● Code review ● Implementing integration with third-party systems ● Writing tests, bugfixig Environment SpringBoot, Hibernate, Java, Documentum, ExtJS, JUnit, Oracle Database. Git, Jira, Confluence, Crucible. Period From: Feb. 2018 To: May. 2018 Project Role Team Leader, project architect Project Lot Laundry Uber Like service for connecting customers and Laundry service providers. Allow users to find nearest, cheapest laundry service providers and place order. Including Admin panel for Laundry administrators and mobile apps for customers. Participation ● Team coordination ● Planning and estimating development process ● Code review ● Implementing integration with third-party systems ● Writing tests, bugfixig Environment SpringBoot, Hibernate, Java, Documentum, ExtJS, JUnit, Oracle Database. Git, Jira, Confluence, Crucible. Period From: Dec. 2017 To: Mar. 2019 Project Role Senior Java Developer, Team Leader Project MedRev The system was designed in a way that makes it possible for one medical company to collaborate with several insurance companies. Each insurance company can set up the structure and the interface of the cases in accordance to its requirements and standards. Participation ● Team coordination ● Project architect ● Planning and estimating development process ● Code Review Environment SpringBoot, Hibernate, Java, Documentum, ExtJS, JUnit, Oracle Database. Git, Jira, Confluence, Crucible. Period From: Jul. 2016 To: Dec. 2017 Project Role Key developer Project Amway Webstore New webstore for Amway (short for The American Way) based on Hybris platform. Amway is American company that uses a multi-level marketing model to sell a variety of products, primarily in the health, beauty, and home care markets. The webstore is fully integrated into Amway business owner (ABO) experience – increased focus on brand building, training, ABO eco system, focus on driving business support and experience. Participation ● Team coordination ● Planning and estimating development process ● Code review ● Implementing frontend and backend functionality ● Implementing integration with third-party systems ● Writing tests, bugfixig Environment Apache Tomcat, SAP Hybris, Apache SOLR, Java, Spring, JSP, JQuery, Node.js, Vue.js, REST, JUnit. This is cross-database solution. GitHub, Jira, Confluence, Bamboo. Period From: Jun. 2015 To: Jan. 2016 Project Role Java developer Project United industrial document management system Redesign of big document management software for Rosatom State Atomic Energy Corporation. Participation ● Developing & integration of controls for project-specific UI framework based on ExtJS ● Code review ● Writing tests, bugfixig Environment Oracle WebLogic, Java, Documentum, ExtJS, JUnit, Oracle Database. Git, Jira, Confluence, Crucible. Period From: Sep. 2013 To: May 2015 Project Role Java developer Project Internal document management system Software developed for Sukhoi Company (JSC) to provide ability to organize internal document management according to company’s business processes. Participation ● Developing application UI and business logic ● Implementing document workflows ● Implementing reporting system ● Performance tuning ● Realizing application migration from Apache Tomcat to WebLogic server ● Code review ● Writing tests, bugfixig Environment Oracle WebLogic, Java, Alfresco, Spring, GWT, Activity, JasperReports, JUnit, PostgreSQL. Mercurial, Jira, Confluence, Bamboo, Crucible. Period From: Nov. 2012 To: Aug. 2013 Project Roles Java developer Project Remote maintenance system for legal entities The software developed for MTS Bank, allows customers to exchange documents with the bank and receive loans. Participation ● Developing application UI and business logic ● Implementing integration with third party systems ● Writing tests, bugfixig Environment IBM WebSphere, Java, Oracle ADF, JMS, JUnit, Oracle Database. SVN, Mantis..
Load more

Recommended publications
  • User Documentation for Crucible 3.4 User Documentation for Crucible 3.4 2
    User documentation for Crucible 3.4 User documentation for Crucible 3.4 2 Contents Getting Started . 5 Supported platforms . 5 End of Support Announcements for Crucible . 7 End of Support Announcement for IBM ClearCase . 10 Installing Crucible on Windows . 11 Running Crucible as a Windows service . 13 Installing Crucible on Linux and Mac . 17 Configuring JIRA Integration in the Setup Wizard . 20 Starting to use Crucible . 27 Using Crucible . 35 Using the Crucible screens . 36 Using the Review Dashboard . 38 Browsing all reviews . 40 Browsing source files . 41 Crucible Icons . 42 Searching Crucible . 43 Viewing people's statistics in Crucible . 48 Browsing projects . 52 Viewing Project Statistics . 53 Changing your User Profile . 55 Using favourites . 55 Using Keyboard Shortcuts in Crucible . 57 The Crucible workflow . 58 Defining your workflow . 63 Roles and Status Classifications . 65 Creating a review . 66 Creating a review from FishEye . 70 Creating a review from JIRA . 71 Creating a review from a URL . 72 Creating a Snippet Review . 72 Creating reviews from the command line . 73 Adding content to the review . 75 Iterative reviews . 80 Creating patch files for pre-commit reviews . 83 Choosing reviewers . 90 Performing the review . 92 Starting a review . 93 Adding comments . 94 Changeset discussions . 96 Flagging defects . 97 Creating JIRA issues from the review . 98 Viewing reports . 99 Review Coverage report . 101 Completing your review . 105 Using the Review History Dialog . 107 Using RSS feeds in Crucible . 108 Using Wiki Markup in Crucible . 108 Tracking Crucible Review Metrics . 113 Using Progress Tracking . 113 Using Time Tracking . 115 JIRA integration in Crucible .
    [Show full text]
  • 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.
    [Show full text]
  • Veni, Vidi, Vici
    Code Review: Veni, ViDI, Vici Yuriy Tymchuk, Andrea Mocci, Michele Lanza REVEAL @ Faculty of Informatics - University of Lugano, Switzerland Abstract—Modern software development sees code review as For example many of them leverage static code analysis a crucial part of the process, because not only does it facilitate techniques, like the ones provided by FindBugs [5], to spot the sharing of knowledge about the system at hand, but it may implementation problems. However, the results from such also lead to the early detection of defects, ultimately improving techniques are poorly integrated in a code review process, as the quality of the produced software. Although supported by we will see later. numerous approaches and tools, code review is still in its infancy, and indeed researchers have pointed out a number of We propose an approach to augment code review by inte- shortcomings in the state of the art. grating software quality evaluation, and more general design We present a critical analysis of the state of the art of code assessment, not only as a first class citizen, but as the core review tools and techniques, extracting a set of desired features concern of code review. Our approach, called Visual Design that code review tools should possess. We then present our vision Inspection (ViDI), uses visualization techniques to drive the and initial implementation of a novel code review approach quality assessment of the reviewed system, exploiting data named Visual Design Inspection (ViDI), illustrated through a set obtained through static code analysis. ViDI enables intuitive of usage scenarios. ViDI is based on a combination of visualization and easy defect fixing, personalized annotations, and review techniques, design heuristics, and static code analysis techniques.
    [Show full text]
  • Documentation for Fisheye 2.8 Documentation for Fisheye 2.8 2
    Documentation for FishEye 2.8 Documentation for FishEye 2.8 2 Contents Getting started . 8 Supported platforms . 8 End of Support Announcements for FishEye . 12 End of Support Announcement for IBM ClearCase . 14 End of Support Announcement for Internally Managed Repositories . 14 Installing FishEye on Windows . 16 Running FishEye as a Windows service . 19 Installing FishEye on Linux and Mac . 23 Starting to use FishEye . 26 Configuring JIRA Integration in the Setup Wizard . 31 Using FishEye . 38 Using the FishEye Screens . 39 Browsing through a repository . 41 Searching FishEye . 44 Viewing a File . 49 Viewing File Content . 50 Using Side by Side Diff View . 51 Viewing a File History . 53 Viewing the Changelog . 54 FishEye Charts . 56 Using Favourites in FishEye . 61 Changeset Discussions . 64 Viewing the commit graph for a repository . 64 Viewing People's Statistics . 68 Using smart commits . 70 Changing your User Profile . 75 Re-setting your password . 79 Antglob Reference Guide . 80 Date Expressions Reference Guide . 81 EyeQL Reference Guide . 82 Administering FishEye . 88 Managing your repositories . 89 Adding an External Repository . 91 CVS . 92 Git . 93 Mercurial . 96 Perforce . 98 Subversion . 101 SVN fisheye.access . 105 SVN tag and branch structure . 106 Adding an Internal Repository . 114 Enabling Repository Management in FishEye . 115 Creating Git Repositories . 117 Forking Git Repositories . 119 Deleting a Git Repository . 122 Setting up a Repository Client . 122 CVS Client . 122 Git Client . 122 Mercurial Client . 122 Perforce Client . 123 Subversion Client . 124 Native Subversion Client . 124 SVNkit Client . 126 Re-indexing your Repository . 126 Repository Options . 128 Authentication . 130 Created by Atlassian in 2012.
    [Show full text]
  • 1. Atlassian Intellij Connector
    1. Atlassian IntelliJ Connector . 2 1.1 Installation and Upgrade Guide for the IntelliJ Connector . 3 1.1.1 License and Copyright for the IntelliJ Connector . 3 1.1.2 Installing the IntelliJ Connector . 4 1.1.3 Upgrading the IntelliJ Connector . 5 1.1.4 Atlassian IntelliJ Connector Release Notes . 8 1.1.4.1 Atlassian IntelliJ Connector 2.1 Release Notes . 8 1.1.4.2 Atlassian IntelliJ Connector 2.0.1 Release Notes . 30 1.1.4.3 Atlassian IntelliJ Connector 2.0 Release Notes . 33 1.1.4.4 Atlassian IntelliJ Connector 2.0 Beta 12 Release Notes . 38 1.1.4.5 Atlassian IntelliJ Connector 2.0 Beta 11 Release Notes . 41 1.1.4.6 Atlassian IntelliJ Connector 2.0 Beta 10 Release Notes . 44 1.1.4.7 Atlassian IntelliJ Connector 2.0 Beta 9 Release Notes . 47 1.1.4.8 Atlassian IntelliJ Connector 2.0 Beta 8 Release Notes . 49 1.1.4.9 Atlassian IntelliJ Connector 2.0 Beta 7 Release Notes . 52 1.1.4.10 Atlassian IntelliJ Connector 2.0 Beta 6 Release Notes . 54 1.1.4.11 Atlassian IntelliJ Connector 2.0 Beta 5 Release Notes . 55 1.1.4.12 Atlassian IntelliJ Connector 2.0 Beta 4 Release Notes . 56 1.1.4.13 Atlassian IntelliJ Connector 2.0 Beta 3 Release Notes . 57 1.1.4.14 Atlassian IDE Plugin 2.0 Beta 2 for IDEA - Release Notes . 59 1.1.4.14.1 Atlassian IDE Plugin 2.0 Beta 2 for IDEA - Upgrade Notes .
    [Show full text]
  • User Guide for Crucible 2.10 User Guide for Crucible 2.10 2
    User Guide for Crucible 2.10 User Guide for Crucible 2.10 2 Contents Getting Started . 4 Supported Platforms . 4 End of Support Announcements for Crucible . 6 End of Support Announcement for IBM ClearCase . 8 Installing Crucible on Windows . 8 Running Crucible as a Windows service . 12 Installing Crucible on Linux and Mac . 15 Configuring JIRA Integration in the Setup Wizard . 19 Starting to use Crucible . 27 Using Crucible . 34 The Crucible workflow . 35 Using the Crucible Screens . 41 Browsing All Reviews . 42 Browsing Source Files . 43 Using the Dashboard . 45 Crucible Icons . 49 Searching Crucible . 50 Viewing people's statistics in Crucible . 55 Browsing Projects . 59 Viewing Project Statistics . 61 Viewing Reports . 63 Review Coverage Report . 66 Changeset discussions . 70 Changing your User Profile . 71 Roles and Status Classifications . 71 Conducting a Review . 73 Creating a Review . 73 Creating a Patch Review . 74 Creating a Review within Crucible . 82 Creating a review from FishEye . 85 Creating a review from JIRA . 86 Creating a Review from a URL . 87 Creating a Snippet Review . 88 Selecting the Files for the Review . 89 Iterative Reviews . 96 Adding Reviewers . 96 Issuing a review . 99 Performing the review . 101 Adding comments . 102 Flagging Defects . 104 Creating JIRA issues from the review . 105 Completing your review . 106 Sending a review's comments via Email . 108 Using JIRA Integration in Crucible Reviews . 110 Using the Review History Dialog . 112 Tracking Crucible Review Metrics . 113 Using Progress Tracking . 113 Using Time Tracking . 115 Summarising and Closing the Review . 116 Transitioning JIRA issues . 118 Moving a Review to Another Project .
    [Show full text]
  • GUI-GSO-411 DOJO Atlassian Tools Acceptable Use Guidelines
    GLOBAL SECURITY OFFICE Document Reference: GUI-GSO-411 Document Version: 1 Effective: January 13, 2020 DOJO ATLASSIAN TOOLS ACCEPTABLE USE GUIDELINES Purpose The purpose of this document is to provide guidance on acceptable use of the business tools JIRA, Confluence, Bitbucket, Bamboo, FishEye/Crucible, and HipChat (collectively “DOJO Atlassian Tools”) for storing and sharing information for business purposes. Applicability These guidelines apply to all employees, temporary workers, interns, and other workers at Publicis Groupe, its agencies, brands, business units and shared service centers, and authorized third parties (freelancers, contractors, consultants, suppliers, etc.) collectively called ‘People’ in this document. Publicis Groupe and its agencies (including brands, business units and shared service centers) are collectively called ‘Groupe’ in this document. Introduction DOJO Atlassian Tools is a cloud service that enables People to securely collaborate on projects and software development from anywhere and on any device. DOJO Atlassian Tools can be used to share content with internal and external teams. DOJO Atlassian Tools comprise of: • JIRA: a project management application enabling teams to plan and track project work, defects, issues, etc. • Confluence: a wiki project teams can use to manage requirements, track decisions to closure, create how-to guides, capture meeting notes, &c. • Bitbucket: a software source code management server based on the popular open-source Git distributed version control technology • Bamboo: a continuous integration (CI) and software deployment tool that ties automated builds, tests, and releases together in a single workflow • FishEye/Crucible: provides software source code repository search, reporting, and collaborative code review capabilities • HipChat: a secure, searchable group chat client that integrates with the other Atlassian tools Acknowledgement DOJO Atlassian Tools are for business use only.
    [Show full text]
  • Atlassian Tools and Services the Way Ahead
    The CO-DO Atlassian Service Vito Baggiolini with a lot of help from Marian Zurek and Niall Stapley With explicit input from: K. Sigerud, C. Roderick, J. Wozniak, S. Deghaye, W. Sliwinski, L. Burdzanowski, M. Pace, R. Gorbonosov, G. Kruk, M. Buttner JC. Garnier (MPE), B. Todd, M. Dudek (EPC), P. Sollander (OP) Outline • Overview of the Atlassian Service • Use cases • History and growth • Work done over the last 2 years • Satisfaction, dependency, shortcoming and requirements • Plans for the next 12 months (code name “PIA”) 2 Outline • Overview of the Atlassian Service • Use cases • History and growth • Work done over the last 2 years • Satisfaction, dependency, shortcoming and requirements • Plans for the next 12 months (code name “PIA”) 3 Atlassian components and relations to external services (IT) MySQL (IT) SVN on demand JIRA Fisheye Crucible Bamboo Confluence Issues + Code Code Continuous Wikis Agile search reviews integration Crowd (IT) E-mail User+group CO testbed service (IT) (GS) managemnt LDAP E-groups Atlassian Component Other CO Component External service 4 Outline • Overview of the Atlassian Service • Use cases • History and growth • Work done over the last 2 years • Satisfaction, dependency, shortcoming and requirements • Plans for the next 12 months (code name “PIA”) 5 TI Operator’s checklist (Wiki) Confluence Wikis 6 CO Exploitation Portal (by Marine) Confluence Wikis 7 Controls operational issues (APS JIRA) JIRA Issues + Agile 8 Issues send by e-mail from E-logbook to JIRA 9 JIRA Kanban board example JIRA Issues + Agile
    [Show full text]
  • Your Business-Critical Atlassian Platform Datasheet
    ATLASSIAN MANAGED SERVICES (AMS) FROM ADAPTAVIST: Your business-critical Atlassian platform datasheet If your organisation relies on Atlassian BENEFITS OF AMS tools such as JIRA, Confluence, Bamboo, Migrating to a fully-managed Atlassian platform offers four BitBucket or Crucible for key business key benefits. processes like application development, • Reduce total cost of ownership whilst having access to a project management or collaboration, 24x7x365 service you need to know that you can depend • Enable your teams to maintain their focus on their core functions on them. • Reduce your risk for services reliant on Atlassian software • Increase your agility – adopt new Atlassian functionality more Atlassian Managed Services (AMS) from Adaptavist offers quickly, scale the platform and use any Add-Ons that you need a way to reduce the cost, complexity and risk of your organisation’s investment in Atlassian software. WHEN ATLASSIAN IS BUSINESS-CRITICAL 3 AMS Many Enterprises find that when their use of Atlassian applications reaches a certain point, maintaining their Atlassian estate is business-critical. Downtime or poor 2 Self-Build performance is unacceptable and costly. We find that these Increasing User Base Atlassian businesses need a partner who can take full responsibility 1 for the availability, health and performance of their Cloud Atlassian solution. Increasing Complexity TRAINING AND PROFESSIONAL SERVICES TIME TO MOVE TO AMS? AMS offers a complete management solution. From 1 Atlassian Cloud is appropriate for smaller organisations. infrastructure, operating system and database to application Low-cost and accessible but with limited functionality and configuration and management, we take ownership of scalability. the platform as well as providing user administration and 2 Self-Build can be a good option for short-term deployments.
    [Show full text]
  • Disaster Recovery
    Atlassian unleashes the potential of every team. Our collaboration software helps teams organize, discuss and complete shared work. Teams at more than 119,000 customers, across large and small organizations—including Citigroup, eBay, Coca-Cola, Visa, BMW and NASA—use Atlassian’s project tracking, content creation and sharing, real-time communication and service management products to work better together and deliver quality results on time. Our products include Jira Software, Confluence, Stride, Trello, Bitbucket, Jira Service Desk and Bamboo. Server to Data Center: The Tipping Point 4 Section I: Scaling Atlassian Applications 11 Section II: The Tipping Point 17 Section III: What is Data Center? 32 Section IV: Prepare, Plan, Execute 43 Section V: Refine 47 Section VI: Hear It From Our Customers 58 Sources and Resources SERVER TO DATA CENTER: THE TIPPING POINT 3 SECTION I Scaling Atlassian Applications At some point in your Atlassian journey you’ll likely find yourself needing to scale your Atlassian applications to a wider group in your organization. This section provides some high-level guidelines for determining growth and creating internal governance before taking the final step in scaling Atlassian: providing true high availability and building a more robust infrastructure to support uptime and performance needs. Keep in mind that there is no ‘one-size-fits-all’ approach to scaling Atlassian applications. Each organization, and team, has different processes, work flows and needs. 4 Determining Scale When considering scaling a single instance of an application like Jira Software, many customers first think about the number of issues their instance can support, ignoring some of the other factors that can contribute to poor performance or increased administration.
    [Show full text]
  • Accurev Plugin for Crucible 2018.1
    AccuRev Plugin for Crucible 2018.1 Installation and Release Notes Micro Focus The Lawn 22-30 Old Bath Road Newbury, Berkshire RG14 1QN UK http://www.microfocus.com © Copyright 2018 Micro Focus or one of its affiliates. All rights reserved. MICRO FOCUS, the Micro Focus logo and AccuRev Plugin for Crucible are trademarks or registered trademarks of Micro Focus IP Development Limited or its subsidiaries or affiliated companies in the United States, United Kingdom and other countries. All other marks are the property of their respective owners. 2018-12-04 ii Contents Contents ................................................................................................................................. 3 Installing AccuRev Plug-In for Atlassian Crucible ............................................................. 4 System Requirements ...................................................................................................................... 4 Prerequisites ..................................................................................................................................... 4 Installation Steps .............................................................................................................................. 4 Configuring Atlassian Crucible (4.3 to 4.6.1) to Use AccuRev ......................................................... 4 Uninstalling AccuRev Plug-In for Atlassian Crucible ......................................................................... 6 Getting Started .....................................................................................................................
    [Show full text]
  • JIRA Software 7.3 Documentation for JIRA Software 7.3 2
    JIRA Software 7.3 Documentation for JIRA Software 7.3 2 Contents JIRA Software documentation . 4 Getting started with JIRA Software . 4 Getting started as a JIRA Software manager . 5 Setting up your workspace . 6 Customizing your project . 8 Creating your backlog . 10 Grooming your backlog . 12 Planning your sprint . 14 Tracking your progress . 15 Wrapping up your work . 17 Doing more with your agile projects . 20 Getting started as a JIRA Software user . 23 Learn to plan and estimate for scrum teams . 26 Plan for the team . 27 Customize the team board . 29 Estimate in story points . 30 Analyze team reports . 32 Optimize future plans . 35 Installing JIRA Software . 36 Using JIRA applications with HipChat . 37 Using JIRA applications with Portfolio for JIRA . 42 Using JIRA applications with Confluence . 45 JIRA Software overview . 48 JIRA applications overview . 49 Leading an agile project . 52 Starting a new project . 53 Configuring a project . 54 Creating a board . 55 Configuring a board . 59 Workflows . 84 Configuring development tools . 85 Customizing the issues in a project . 87 Configuring collaboration tools . 88 Organizing work with components . 89 Building a backlog . 90 Using the backlog . 91 Planning a version . 93 Configuring versions in a Scrum project . 94 Configuring versions in a Kanban project . 96 Working with epics . 96 Linking a Confluence page to an epic . 98 Getting to work . 99 Running sprints in a Scrum project . 100 Planning sprints . 101 Monitoring the progress of a sprint . 104 Completing a sprint . 106 Reopening a sprint . 108 Linking a Confluence page to a sprint . 111 Checking the progress of a version .
    [Show full text]