Category: versionone

VersionOne – Edit Story ”; Previous Next In this chapter, we will learn how to edit story in VersionOne. Editing a story consists of many actions. With the Edit Story feature, we can modify the details of the story, close it, delete it, add it into the watchlist, block it with issues or defects, convert into defect, etc. In this chapter, we will discuss how to go about editing story details, closing a story and deleting a story. Edit Story Details While editing the story details, a user can edit the details of the story including title, priority, estimation and dependencies. The only field that remains unmodified is the unique id of the story; it can never be changed or modified. There are three ways to edit a story. The ways are described as options below − Option 1 It is recommended to quickly edit title, story points, projects, priority, owner and order. Follow these steps in Option 1 for editing a story. Go to the Product Planner → Backlog. It opens the backlog page. Double-click on row to make the column editable. The column changes from view only to edit mode. After editing, click on the Save button. It saves all the modified details of the corresponding row. The following screenshot displays how to edit by taking up Option 1 − Option 2 Follow these steps under Option 2 for editing a story. Go to Product Planner → Backlog. Click on the Edit button present corresponding to each row. It will open the story details in the Edit mode. After editing, click on Save/Save & View. It saves all modified details of the corresponding story. The following screenshot displays how to access the edit functionality − Option 3 Click on Story Title/ID to open the Story Details page. Clicking on the Pencil icon next to the field makes the field editable. Make the appropriate changes and then press Enter/Return on the keyboard. It saves the modified details of the respective field. The following screenshot shows the edit functionality at the story detail page − Close a Story Once all tasks of a story complete, it can be closed to claim the work done in the sprint. A closed story can be re-opened later if required. In this section, we will discuss how to close a story. Closing a story shows that all the work related to the story is complete. Once a story is closed, a user can re-open it if additional changes are required in future. Quick close updates the status of story and closes it in a single click. There are many ways to close a story. We will discuss the ways as options below. Option 1 Go to Product Planner → Backlog.. Click on the Edit dropdown present corresponding to each row. Select Close or Quick Close as shown in the screenshot below:. If a user selects Close, it opens an additional window. Here, select status and click on the Close Backlog Item button as shown in the screenshot below − Option 2 Click on Story Title/ID to open the Story Details page. Click on the Edit dropdown. It displays all the available options. Select Close or Quick Close as shown in the screenshot below. If a user selects Close, it opens an additional window. Here, select a status and then click on the Close Backlog item. Upon selecting the Quick close option, it directly closes the story. Delete a Story A deleted story cannot be tracked and visualized later. Deletion usually happens if a story is not needed or if it is duplicate. In this section, we will discuss the deletion of a story. If a story is created in error or duplicate, it should be deleted. For tracking the story, it must be closed instead of deleted. Deleting a story hides all of its references. If a story is deleted, the child items like link, attachments, task or test sets also get deleted. Following are the steps to delete a story − Go to Product Planner → Backlog.. Click on the Edit dropdown present corresponding to each row. It displays the available options to take action. Select Delete as shown in the screenshot below − It will open the read only detail of the story with Delete button. Click on the Delete button as shown below. As soon as the button is clicked, the story gets de-listed from the backlog item and all of its references will also be deleted. Similar steps as performed above can be followed to delete the story from the Story Detail page. Click on the Story title/id to open the story detail page. Click on the Edit dropdown and select Delete. It will open the read only detail of the story with the Delete button. Click on the Delete button. Print Page Previous Next Advertisements ”;

VersionOne – Sprint Scheduling ”; Previous Next The first step in the Iteration/Sprint planning process Iteration/Sprint Scheduling. In this step, the team selects the amount of work it can deliver from the prioritized backlog. The Team makes use of the historical velocity as a guide reference to commit the work. This helps the team determine how much to schedule in each sprint. To access Sprint Scheduling, from the main menu, select Team Planner → Sprint Scheduling. Add a Sprint It is the job of a Project Owner or Scrum Master to add a sprint. Sprint is added well before the start date and it clearly mentions the start and end dates to achieve the committed goals. Follow these steps to add a sprint into the project − Navigate to the Sprint Scheduling. It opens the Sprint Scheduling page. Select the Project in Project Navigator. It selects the project where sprint has to add. After that, click on the Add Sprint button present at the left side as shown in the screenshot below. It opens the Add Sprint form. Enter the required and optional fields. Required Fields − Title, Begin Date and End Date. The End Date should be a future date. Optional Field − Description, Owner, Target Estimate Points, Change Comments. After that, click on the Save button. It adds the new sprint into the project. The following screenshot shows how to add sprint − A user can start adding items into sprint by dragging from the right and dropping at the left. View & Edit Sprint Details From the Sprint Detail page, a user can view all the information associated with sprint and edit the information if required. While editing the sprint details, a user can edit all the details of the sprint including title, priority, date and description. Following are the important steps to view & edit the details − To access the Sprint Detail page, navigate to Sprint Scheduling and hover over on the Sprint Name at the left side. It displays the sprint name and the limited details into additional pop-up. Click on the Sprint Name in the pop-up as shown in the screenshot below − It displays the Sprint Details page. It has different links like Backlog, Defect, Tasks, Tests, Link and Attachment to view the respective details. The Following functionalities can be used in the details page − If a user wants to… Do this… Access the Sprint Scorecard Click the Scorecard tab. View the sprint change history Click the History tab. Close the sprint Select Close from the Edit dropdown button. Change the state of the sprint to Future Select Future from the Edit dropdown button. Delete the sprint Select Delete from the Edit dropdown button. If the Delete button is not available, it means that the sprint still contains items. The following screenshot displays the different functionalities of the Sprint Detail Page − Print Page Previous Next Advertisements ”;

VersionOne – Quick Guide ”; Previous Next VersionOne – Introduction VersionOne is a web-based project management tool used by testers, developers and other stake holders to manage, track and organize software testing efforts. It follows and covers full life cycle of Agile Methodologies. It supports from first step as Product Backlog to the project’s final step as completion and delivery. Interesting Points VersionOne supports a wide range of functionalities and is one of the best available project management tools for Agile. VersionOne is joining CollabNet to bring DevOps into the table. Following are a few interesting facts about VersionOne − VersionOne helped to bring the Agile Management tool in 2002. VersionOne is also known as the Agile Management tool. It is developed and copyright by VersionOne Inc. VersionOne is a web based tool that supports all browsers especially Chrome, Firefox, IE etc. It supports different windows OS like Windows XP, Vista, 7, Mac, etc. VersionOne provides 30days trial period. It supports all phases of planning, scheduling, collaborating, tracking and reporting for projects, releases, iterations, epics, stories, defects, tasks, tests, teams and team members. VersionOne was named as one of the Best Places to Work by the Atlanta Business Chronicle. Now, CollabNet and VersionOne have merged to accelerate innovation across Enterprise Software Development and Delivery in 2017. VersionOne can be customized using various methodologies such as SAFe, Scrum, Kanban, Lean, XP, and DAD. License and Free Trial VersionOne is used at commercial level across various software industries. It allows the new users to go through the tool by providing limited free access. In this section, we will see how VersionOne connects with different user groups at personal and commercial level − VersionOne is a commercial tool and available as Trial version for a limited period of 30 days. For personal use, a user can register and get a hands-on experience of VersionOne. To utilize VersionOne services, a license is required. After 30 days, if a user wants to continue using VersionOne, a license is required. By purchasing one of the products, VersionOne provides license key to continue for a certain time period based on purchase agreements. VersionOne provides free license for 30 days for cloud based access as well as local server set up. User can set up host server into his local machine as well by following installation guidelines and fulfilling pre-requisite. VersionOne Uses There are a wide range of benefits and usage of VersionOne depending on team size, type of work and other factors. The benefits and usage are listed below − VersionOne is used in tracking all QA activities from the 1st phase of software testing lifecycle in Agile. Tracking can be started from adding the requirements to accepting the requirement by the Product Owner. VersionOne is useful in Project Management, Defect Management and to customize into different agile methodologies as per the requirements. A user with proper role can customize the VersionOne fields, boards, reports, displays according to project requirement and standards. In addition to the above, VersionOne also supports agile portfolio management, product road mapping, regression test management, customer idea management, agile visualizations and custom reporting and analytics. It supports all macro level activities performed by QA. VersionOne is very useful in performing QA tasks like planning, scheduling, collaborating, tracking and reporting for projects, etc. VersionOne Specifications The base of VersionOne is combined with different and latest technologies and ideas. To use a developed VersionOne tool, hardware and software supports are required at Server as well as Client side. Following table lists down important specification of VersionOne − Sr.No. Specification Description 1 Application copyright It is taken by VersionOne Inc. It provides Commercial and Trial Version. 2 Tool scope It can be used as Project Management and defect tracking It is utilized as Agile Management Tool 3 Testing Methods Agile Testing Automation testing Exploratory Testing Functional/Manual Testing 4 Tool Objectives Complete life cycle of Agile Methodologies Desktop Testing Web Testing Report statistics 5 Management Features Product Backlog Resource Management Defect Management Project Management in Agile Reporting 6 Hardware Requirements for Server CPU: Dual Core 2GHz and latest Memory : 4GB and aboveRAM 7 Error Handling Capture screenshots 8 User interface Available Plugin GUI usability Mobile UI Server and Web based VersionOne – Features In this chapter, we will discuss the different features of VersionOne. The main feature of VersionOne is to attract QAs and other stakeholders for Agile management. VersionOne Core Features VersionOne provides a wide range of features that prove beneficial to the Agile Project team. It does not only support Project management but also how to do day to day activities in case team is not situated locally. It provides a software solution to implement agile within the globally situated team. Following table lists down the core features of VersionOne − Sr.No. Core Features Description 1 Testing Supports VersionOne supports the following test methodologies − Agile Testing − Full Life Cycle Black box testing Exploratory Testing Functional/Manual Testing Automation Testing 2 Centralize & organize VersionOne tool can create, centralize, organize and manage test cases very effectively and efficiently. It can easily import test cases from Excel and other management tool. It can create multiple versions of test cases for comparison and uses It can do planning of releases and sprints. 3 Manage & Track Progress It supports build out and re-run of test execution suites. It kicks off automation suite as well. It captures step-by-step progress of sprint/release with detailed explanation. It supports day-to-day progress and individual contribution. 4 Notification Email can be sent for a particular task/communication to users. Voting and watching features to keep an eye on progress for stakeholders. Use @mention to get attention of specific team member at Comments/Description. 5 Power Search VersionOne supports powerful search functionality with Hotkeys features. Supports free text search. Supports syntax search. 6 Reports VersionOne supports multiple reporting. It supports Burndown, Velocity and Test Trends report. Generate detailed summary report for projects, release and sprints. Track the workload of entire team

VersionOne – Product Planner ”; Previous Next Product Planning is the actual start of the project. In this phase, Product Owner works with backlog items to prioritize, groom and estimate. In this chapter, we will discuss how to plan the backlog items and how to manage them in the sprint level. Points to Note In this section, we will go through some important points that need to be considered in product planning. Product Planning is the activity where Product Owners identify, organize and groom the Backlog to prepare it. The development/testing/BA team(s) works on this aspect. If planning does not happen properly, sprint works affect the productivity and timeline of project.. It involves managing the backlog items, test sets and defects that define the updates going into the product. These items form the backlog and are ranked by priority so they can be scheduled into releases/projects and sprints. Product Planner is divided into two sections – Planning and Input. The Planning section consists of − Backlog − It is used for planning and prioritization of Agile backlog in list view. Backlog Groups − It provides the hierarchical functional groupings used to segment the backlog. Backlog Goals − It provides the measurable targets to drive the project effort into a proper direction. The input section consists of − Requests − These are generated by customers/stakeholders who approve the assets/backlog. Issues − It captures roadblocks or dependencies or other issues that affect the project directly or indirectly. Regression Tests − These are templates for Acceptance Tests. Templates − It is the standard template that is used to configure stories/defects/backlog items. Import − It is the standard template that is used to configure stories/defects/backlog items. Print Page Previous Next Advertisements ”;

VersionOne – Add a Project ”; Previous Next In this chapter, we will see how to add a project in VersionOne. Project is the backbone of a Project Management tool. Project represents a set of items and tasks that should be completed in a defined time to consider it as completed. Until a project finds its existence, none of other functionalities/tasks can be performed. Project groups all sprints/backlogs/tasks/issues etc. into one place. In this chapter, we will discuss about adding a project into VersionOne. To add a project, a user should have the System Admin role. Create a Project Project helps to maintain hierarchy of all sub-items like backlog, defects and issues in order to complete it in the defined time. These are useful to centralize multiple backlog as well as relationship with project. In this section, we will discuss the steps performed to add a project into VersionOne. The steps are as follows Login as Admin and Go to the Settings, present at right top,and select Project & Field Admin → Project as shown in below screenshot. It opens the Project page and displays all available projects in the hierarchy. It will not display any project in case none of the project is added before. Expand the System (All Projects). Click on the Add Child Project button next to the parent project under which user wants to create the new project as shown below − It opens the add project form where a user needs to enter the details in the different fields − Field Action Description Title Type the name of the project. The name of the project/release as it displays in the Project Tree. Parent Project This field is pre-populated with the name of the parent project. Click on the name to view additional details. The name of the project that is one level higher in the Project Tree hierarchy. Iteration Schedule Click on the magnifying glass to assign an Iteration Schedule to the project. The Iteration Schedule assigned to the project.. Planning Level Select one of the following − Enterprise Portfolio Value Stream Release Train Program Increment Indicates how the specific node is being used in the Project. When this attribute is set on a Project, any new child project will automatically be assigned the next value from the list. Description Type a narrative description of the project This is a rich text field that allows to add expanded details about the project. Budget Type in the budget amount The allocated budget amount for the project/release. Begin Date The date the project begins. The date the project begins. This field is required. End Date The date the project ends. The date the project ends. This field is optional. Status Select the status of the project. Indicates the status of the project. Owner Type the first three characters of the project owner”s name. The person to contact if any questions. Target Swag Type in the Swag amount. The amount of Swag user expects to be delivered in the project. Useful when planning. Target Estimate Points Type in the Target Estimate amount. The amount of Estimate you expect to be delivered in the Project. Useful when planning. Test Suite Select a TestSuite from the dropdown list. The TestSuite assigned to the project. Pipelines Select a Pipeline from the dropdown list. Pipelines assigned to the project. Reference Type any additional project information. Free form short text field for information about the project. Now click on Save/Save & New/Save & View as shown the screenshot below − After clicking on Save, project gets listed as shown in the screenshot below. There is Move, Edit, Close and Delete button as well to edit project details and delisted to the project. Print Page Previous Next Advertisements ”;

VersionOne – Portfolio Planner ”; Previous Next Portfolio Planning is used to focus on high level planning. It consolidates the Portfolio Planning, Prioritizing, Tracking and Estimating functionalities. In this chapter, we will discuss about Portfolio Tree, Roadmaps, Kanban board and Timeline. Portfolio Tree and Roadmaps are used at Planning phase while Kanban Board and Timeline are used to track the progress. Points to Note In this section, we will discuss how to access Portfolio and the different sub-items. Portfolio consolidates portfolio planning, their tracking, prioritizing and estimating functions. A user can access Portfolio planning by navigating Portfolio → Planning. Similarly, tracking and planning rooms can be accessed as shown below − Portfolio Planning consists of Portfolio Tree, Roadmaps, Budgets and Strategic Themes. Portfolio Tracking consists of Kanban Board, Project Timeline and Value Stream Board. Portfolio Tree Portfolio Tree represents the Portfolio items into hierarchy – High level to Granular level. It is like Parent-child tree where each Portfolio item is situated under parent item. In the hierarchy/tree, the portfolio present at top is the highest level and decrease step by step for the next item present under that. In this section, we will discuss how the portfolio tree works. The Portfolio Tree (formerly known as the Epic Tree) allows defining and evaluating the functional hierarchy of features. A user can prioritize the features based on their relative value and high-level cost. Whenever required, a user can decompose portfolio items into one to many detailed levels of sub-portfolio items and backlog items that can be delivered by the teams. While the team works at the backlog items, the Portfolio Tree tracks the progress of the portfolio items. The following screenshot displays the Portfolio tree − To add a new Portfolio hierarchy, user can click on Add Portfolio Item present at right top. To add a portfolio item into existing hierarchy, click on the Add Child Portfolio Item on the corresponding level, present at the right side of each portfolio as shown below. It opens the Add Portfolio form where user provide details and click on Save. Roadmaps Roadmaps provide a flexible way to display important milestones to stakeholders. It is used to set high level target in defined time. In this section, we will discuss the features of Roadmaps and how it works. Roadmap is used to keep update the team about progress. It keeps stakeholders in the loop so that they can understand current priorities and timing and track how their needs will be fulfilled over time. It provides better feedback into the planning cycle with respect to how stakeholder priorities the requirements. To access the Roadmaps, navigate to Portfolio → Planning → Roadmaps. It has 2 different layouts − Board and Timeline The following screenshot displays the Board Layout view − The following screenshot dispalys the Timeline layout with respect to the start date and the end date − Kanban Board Kanban board is one of the important features designed to track the progress of any project. In Agile methodology, a team can track even day to day activities and progress at backlog items in the Kanban board. In this section, we will discuss the different features of Kanban board − Kanban board is used to visualize, plan and track the progress of the portfolio items and the child items. It provides a board view with categorization as None, Define, Breakdown, Build, Test and Deploy. Either of the backlog items/portfolio can be categorized among these based on the progress. To access it, navigate to Portfolio → Tracking → Kanban Board. By default, each card shows the ID, title, owner (if applicable), and the Swag (high level size estimate). A user can have the basic details of the card by just viewing the Kanban board. By clicking on the card title, they can view the details of the item. A user can drag and drop a portfolio item card to another place in the same column (to prioritize the ranking) or move it to another column (to update the status). Click on the down arrow in the top right corner of a card for access to common the actions as follows − Edit portfolio item details − It will allow to edit the details of the item. View portfolio item dashboards − It will open all the details in the view mode. Block portfolio items − It will block the portfolio item and ask the blocking reason. Even a user can link it with blocking issues/defects/dependent story. Close portfolio items − It is used to close the item. Later, it can be re-opened if required. Watch portfolio items − It is used to add the item in the watch list and get notification if there is any change; the change can be with the status too. The following screenshot displays the Kanban Board − Project Timeline Project Timeline can be accessed as Portfolio → Tracking → Project Timeline. Project Timeline can be used for the following − Plan and communicate current and future project delivery. View historical delivery of projects. To see the next level of detail, priorities, and progress from a single view. Understand the organizational velocity achieved in delivering previous projects that can be used as a guide in planning future work. Project Timeline provides graphical view of projects. It displays the scheduling and delivery of work initiatives, features, and sub-features for specific projects. The following screenshot displays the Project Timeline’s view − Print Page Previous Next Advertisements ”;