Version One Highlights

  • 883 views
Uploaded on

Highlighting the capabilities of Version One

Highlighting the capabilities of Version One

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
883
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • This presentation tries to impart very basic information about Version One, Agile Project/Product Management tool.This presentation may contain materials that are procured from external sources.Please reach out to me in case you find any material that is been used infringes upon someone’s copyrights.

Transcript

  • 1. Agile Series by NishanthVersion One Highlights
  • 2. Snapshot
  • 3. Features Available• Administrations• Product/Project Planning• Release Planning• Sprint Planning• Sprint Tracking• Sprint Review & Retrospective
  • 4. Start
  • 5. How to begin• Create Project• Create Member• Assign member to Project• Begin Project
  • 6. Create Project
  • 7. Create ProjectFirst thing we need to do is to create a new project or add a child project to an existingproject. To create a new project/child project,• Click on the Projects Menu item• Click on the Add Project button to create a new project• In the popup window that opens, enter the following details– Title– Description– Begin Date– Owner• Press Ok to confirm the changes
  • 8. Create Project – Nova Music Store
  • 9. Create Sprint ScheduleSprint Schedules determine the duration of the sprints as well as the gaps between anytwo sprints. To create a new schedule,• Click on the Sprint Schedules Menu item• Click on the Add Sprint Schedule button to create a new schedule• In the popup window that opens, enter the following details– Title– Sprint Length (in Days/Weeks/Months)– Sprint Gap (in Days/Weeks/Months)– Description, if any.• Press Ok to confirm the changes
  • 10. Create Sprint Schedule – Nova Music Store – Online Store
  • 11. Assign Member RolesOnce the project is created, the next step is to identify the team and their roles.• Click on the Member Roles Menu item• Click on the Manage against each project/sub-project present to manage the team• In the popup window that opens, select the roles of each team member• Close window once roles are assignedNote:- If no team members are found, then please go and add team members from Teams option
  • 12. Assign Member Roles
  • 13. ProgramsWe need to create releases that need to be managed in the system. For that,• Click on the Programs Menu item• Click on the Add Program to create and manage• In the popup window that opens, enter the title and Click Ok.• Once the Program is created, click on Manage Projects button against the programto select the projects that need to be managed• Close window once projects are selected
  • 14. Programs
  • 15. Programs
  • 16. Test SuitesWe need to create Test Suites to manage the testing aspects of the project. For that,• Click on the Test Suites Menu item• Click on the Add button to create a new test suite• In the popup window that opens, enter– Title– Reference name– Description• Click Ok to save the changes
  • 17. Test Suites
  • 18. Members
  • 19. Add MemberWe need to create team members in the system who will be working on the project.• Click on the Members Menu item• Click on the Add Member button to create a new member• In the popup window that opens, enter the following details– Name of the member– Short name that will be displayed– User name with which the member will logon to Version one– Password– Default Role– Rest are optional• Click Ok to save the changes or Ok and New to save and create a new member
  • 20. Add Member
  • 21. Project AssignmentWe need to assign projects to the members so as know who will work on what. For that,• We can either drag n drop members to projects OR• Select members and click on Assign to Projects button• In the popup window, select the project from the drop down menu• Click Assign button to save the changes
  • 22. Project Assignment
  • 23. Project RolesWe need to assign projects to the members so as know who will work on what. For that,• Click on Manage button against the member that need to managed• Expand the Projects and select appropriate Role from the drop down menu• Close the window once the changes are made
  • 24. Project Roles
  • 25. Member GroupsMember groups are used to keep track of the various business roles that are present inthe organisation. To create a group,• Click on Add Member Group button• Enter the title and Description• Click Ok to save the changes and close the window
  • 26. Member Groups
  • 27. Teams
  • 28. Add TeamOnce the project is created, we need to create teams in the system that will be workingon the project.• Click on the Teams Menu item• Click on the Add Team button create a new team team• In the popup window that opens, enter the following details– Title of the team– Description• Click Ok to save the changes
  • 29. Add Team
  • 30. Product Planning
  • 31. Product Planning• Backlog• Epic Tree• Feature Groups• Goals• Goal Assignment• Requests• Issues• Templates• Import
  • 32. Backlog• The Backlog item and Defect Planning page provides a flexible, editable listing ofall the available backlog items and defects contained in the currently selectedproject and all of its subprojects.• New backlog items and defects can be entered and existing items can be edited,filtered, sorted, categorized and ordered relative to one another.• The Backlog item and Defect Planning page is used to build the backlog of backlogitems for each project and identify defects to be addressed• Add Backlog– Click on Product Planning->Backlog– Click on Add Backlog Item Inline/Add Backlog Item to create a new backlog item– Enter date in the mandatory fields– Click Ok to save changes
  • 33. Add Backlog
  • 34. Add Backlog Inline• Click on Product Planning->Backlog• Click on Add Backlog Item Inline to create a new backlog item• Enter the mandatory data and click Save button to save
  • 35. Epic Tree• Epic Breakdown allows you to break a single backlog item down into smallercomponents that may be spread across projects, releases, teams or sprints.• Breaking down a story, in effect, retires the original epic backlog item in favour ofthe newly created child backlog items and allows you to manage the relationshipsup and down the epic hierarchy.• Add Epic Tree– Click on Product Planning->Epic Tree– Click on Add Epic to create a new epic– Enter the mandatory fields and click Ok to save the changes
  • 36. Add Epic Tree
  • 37. Add Child Epic
  • 38. Feature Groups• Feature groups are functional groupings of backlog items.• Feature groups can be used in filtering throughout the planning and trackingprocess and can be used to report on progress and plans from this higher levelfunctional perspective.• The Feature Group Assignment page in Product Planning provides a location inwhich to create new feature groups, assign backlog items to feature groups, andeven to organize the feature groups into a hierarchy if desired• Add Feature Groups– Click on Product Planning->Feature Groups– Click on Add Feature Group to create a new feature– Enter the mandatory data and click Ok to save the changes
  • 39. Add Feature Group
  • 40. Goals• The Goals page lists all available goals for the selected project, allows the user todesignate which goals are targeted by the project and provides a view of theprogress of each of the goals within the selected project.• Select Product Planning in the main menu. Set project context to be the level atwhich goals will be measured.• Define the strategic goals and objectives to be targeted by the project.• Associate project work with the goal(s) it supports.• Add Goals– Click on Product Planning->Goals– Click on Add Goal to create a new goal– Enter the mandatory data and click Ok to save the changes
  • 41. Add Goal
  • 42. Requests• The Request Planning page provides a flexible, editable listing of all the availablerequests contained in the currently selected project and all of its subprojects.• New requests can be entered and existing requests can be edited, filtered, sorted,categorized and ordered relative to one another.• The Request Planning page is used to collect feature requests submitted to the team.• Define requests collected from external and internal sources for additional featuresand/or enhancements.• Generate new backlog items from approved requests.• Add Request– Click on Product Planning->Requests– Click on Add Request to create a new request– Enter the mandatory data and click Ok to save the changes
  • 43. Add Request
  • 44. Issues• The Issue Tracking page provides a flexible, editable listing of all the availableissues contained in the currently selected project and all of its subprojects.• New issues can be entered and existing issues can be edited, filtered, sorted,categorized and ordered relative to one another.• The Issue Planning page is used to collect and document high level issues that canor will impact the on-going performance and delivery of the team.• Define issues identified by the team that can hamper team performance or delivery.• Add Issues– Click on Product Planning->Issues– Click on Add Issue to create a new issue
  • 45. Release Planning
  • 46. Release Scheduling• The Release Planning process is used to move backlog items and defects throughthe project hierarchy.• Select Release Planning in the main menu.• Schedule backlog items and defects in releases by clicking and dragging a row ingrid at the bottom up into the appropriate Release (sub- project) container above.• To remove backlog items or defects from a release, display the detailed list in therelease container, then click and drag a row from the container into the largerproject container that surrounds the entire top section of the page.• To move backlog items or defects from one sub-project to another, drag the rowfrom the detailed list into another sub-project container on the page.• Add Issues– Click on Release Planning->Release Scheduling– Click on Add Child Project to schedule a new release
  • 47. Schedule New Release
  • 48. Team Scheduling• The Team Scheduling page is used to allocate workload across the various teamsworking on the project.• Select Release Planning in the main menu.• Select the Team Scheduling page.• Assign backlog items and defects to a team by clicking and dragging a row in gridat the bottom up into the appropriate Team container above. If the team is notvisible, you can also drag onto a row of the All Teams list at the left to make theassignment.• To remove backlog items or defects from a team, display the detailed list in theteam container, then click and drag a row from the container into the larger projectcontainer that surrounds the entire top section of the page.• To move backlog items or defects from one team to another, drag the row from thedetailed list into another team container on the page.
  • 49. Team Scheduling• Add Team– Click on Add Team button to create a new Team
  • 50. Release Forecasting• To create forecast reports based on the team’s velocity and remaining estimate
  • 51. Sprint Planning
  • 52. Sprint Scheduling• Sprint Scheduling is the first step in the Sprint Planning process. Sprint Schedulingallows the project team to select a list of backlog items to be delivered within thesprint.• Sprint Scheduling can also optionally be used to schedule work on specific defectswithin the sprint.• Select Sprint Planning in the main menu and the Sprint Scheduling page in the sub-menu.• Set project context to the appropriate scheduling project.• If not already done, assign or create a new iteration schedule for the project.• Enter sprints by selecting Add.
  • 53. Sprint Scheduling
  • 54. Capacity Planning• Select Sprint Planning in the main menu and the Capacity Planning page in the sub-menu.• Use the historical reporting to gauge each team members historical capacity andfactor in any known impacts (training, holidays, etc.) for the upcoming iterations.• Enter capacity for each team member in terms of Detail Estimate expected to becompleted.
  • 55. Capacity Planning
  • 56. Sprint Tracking
  • 57. Detail Tracking• Select Sprint Tracking in the main menu and the Detailed Tracking page in the sub-menu.• This page gives information about the sprint as a whole• It shows the total estimate, total capacity, total done, etc.• Users can choose a different sprint to view its status• Developers can enter the Effort spend as well as TODO and save it.
  • 58. Detailed Tracking
  • 59. Storyboard• Select Sprint Tracking in the main menu and the Storyboard page in the sub-menu.• This page displays the progress of the stories that were drafted into the currentsprint.• The available states for a given story is Future, In Progress, Done, and Accepted
  • 60. Storyboard
  • 61. Taskboard• Select Sprint Tracking in the main menu and the Taskboard page in the sub-menu.• This page displays the progress of the tasks inside the stories that were drafted intothe current sprint.• The available states for a given Task is Future, In Progress, Done, and Accepted• The developer can also create new and edit existing tasks.• The developer can either drag n’ drop tasks between the available states or edit thetask to update the state.
  • 62. Taskboard
  • 63. Taskboard – Edit Task
  • 64. Taskboard – Add Test
  • 65. Sprint Review
  • 66. Close Sprint• Select Sprint Review in the main menu and the Close Sprint page in the sub-menu.• This page displays the available active sprints.• We can choose to close the sprint that got over recently and click the Close button.
  • 67. Retrospectives• Select Sprint Review in the main menu and the Retrospectives page in the sub-menu.• This page helps the team to capture the retrospective notes for the sprint that wasjust closed.• Click on the Add Retrospective button to start capturing the notes
  • 68. Retrospectives
  • 69. Thanks!Exciting new transitions