Project Management Framework

Transcription

1 Project Management Framework Release Notes Version Framework Overview The Project Management Framework (PMF) is a powerful Project Management application designed for the management of Scrum projects. You can jump start your product planning with the ability to import project data directly from a PRPC Application Profile or Microsoft Excel. The PMF scrum board, reporting, and documentation features improve visibility into your project plans, progress and status. PMF also improves the productivity and monitoring of PRPC development cycles enabling teams to update their progress and effort on assigned tasks and bugs directly from the Developer Studio. About this Release The following improvements and enhancements are included in this release of the framework. Features and Benefits for Product Owners A RELEASE ROADMAP displays on the My Products dashboard and on the Release tab of Products. Two additional release statuses, Pending-Planning and Open-Hardening, allow better tracking of the current status of your release. The role of Release Manager can be added to a release team. A Bugs & Issues tab and a Stories tab appears on releases that displays a list of bugs and open stories associated with the release and allows you to: sort and filter the list take action on the rows in a list create or import additional bug and stories to the release bulk process the bugs or stories. A My Epics view on the portal displays a list of epics that you are either a party to or following. Warning messages appear on the dashboard of a release when: a release does not have a development start and end date which are required to create a burndown chart for the release. a release start date is in the future to indicate that burndown data cannot be recorded until a start date is entered. burndown data is no longer being recorded for the release to indicate a release date is more than four weeks in the past. Release Notes 1

2 Feedback/Ideation Improvements You can filter a feedback list to view only the feedback items that you have LIKED. The count of LIKES for a feedback item displays in the header of the feedback item. Two additional statuses, Pending-Input and Open-InReview, are available to track the progress of feedback items. A Quick Edit action is available from the row actions of a feedback list allowing you to edit basic information about the feedback item including the name, category, requested by, and status. You can resolve a feedback item as a duplicate of a bug, task, issue, story, or epic. The two items are linked to each other and followers of the feedback item are added as followers of the duplicate item. Additional Feedback reports on the product Dashboard tab report feedback by current status, creator, category and count created by day. Scrum Team Features Teams can create a Definition of Ready that can be viewed from a project, sprint, or user story. Teams can create a default team task list that can then be added to multiple or individual stories in a sprint. Sprint Process Improvements You can import your team s task list into the open stories in your sprint using the Add Task to Stories action. You can import your team s task list to individual stories using the Add Tasks to Story action to help ensure that tasks cover all acceptance criteria. The action still allows you to import tasks from Excel or add them manually to the grid. You can view basic details such as description and acceptance criteria. You can also set priority on the tasks. A Quick Edit action from the row of a task list allows you to edit the name, category, remaining effort and status fields of a task. A Claim this task action from task lists allows you to quickly assign a task to yourself and set its status to Open. Warning messages appear on the dashboard of a Sprint when: a sprint has not started or the start date of the sprint is in the future to help teams understand why burndown data is not associated with a sprint. burndown data is no longer being recorded for the sprint to indicate that an end date is more than two weeks in the past. Release Notes 2

3 Bug Processing Improvements A new user preference automatically follows bugs that you create when you choose this option. This improves upon the feature introduced in PMF 7.1 that automatically followed bugs for any user creating a bug. A Mark as Blocked action for bug items prompts the user to enter notes about why a bug is blocked and provides the option to link to a dependent item that is blocking the current item. On the scrum board, dragging and dropping a bug or issue to the Blocked column of the scrum board displays the Mark as Blocked screen. A Blocked Bug Aging report is available on the Dashboard tab of releases and projects to report the blocked bugs. The Edit Dependencies action is now available from the ACTIONS button on the bug screen. This action is also available on issues, tasks, user stories, and epics. A warning message displays on the bug resolution action if a resource attempts to resolve a bug with a status other than Complete/Fixed that has an open successor dependency. This feature raises awareness that there are people waiting for this bug fix to unblock their work. The Severity, Type, and Reported By fields on the bug entry screen now default to blank to allow for more accurate entry of this data. Improvements to Following Items User preferences allow you to choose if you want to receive status change s on bugs and user stories that you are following. A Bulk Unfollow capability is available from the MY FOLLOWED Items gadget on the dashboard to allow you to either unfollow the resolved items on your list or unfollow selected items Prerequisites The software required to install and run the framework is: PRPC 7.1 ML6 This release supports communication links between PMF and PRPC development systems running the following PRPC versions. 5.5 SP1 5.5 SP2 6.1 SP1 6.1 SP SP1 Release Notes 3

4 6.2 SP SP1 7.1 Supported Databases The databases supported in this release are: Oracle MS SQL UDB PostgreSQL Known Issues Because of the competitive, fast-paced nature of enterprise software development, it is not always possible to address every issue, interoperability concern, or imperfection in every release of a product. Pegasystems' primary goal is to ensure the success of our customers. This table describes the known issues that may occur in this release. ID BUG BUG BUG BUG Bug BUG BUG Description There are issues attaching files to work items when using the Safari browser. When launching attachment modal from attachment icon in a list of items, the file isn t attached when the user clicks Save. Skin/Styles are lost if the user clicks Save in a Save/Discard/Cancel modal. If a user gets validation messages due to invalid data and then clicks to Close the work item screen rather than fixing data and clicking save, the user is presented with a dialog indicating that changes have been made and aren t yet saved. If the user clicks the Save button in this modal, the harness is repainted without styles applied. If a user has viewed the main pulse feed on an item such as a release or backlog and then attempts to add a pulse post to a child item via the pulse icon on the item list, the post will fail. The user will have to navigate to the child item and make the pulse post directly there. Pulse posts can still be viewed from the list pulse icons. Error message is thrown on selecting a release from the Release auto-complete field on the Quick Edit action for an epic. In Firefox browser, if importing an Excel template with 500+ bugs, an Unresponsive Scripts warning message is shown. Bugs still import correctly. Scrum Board is not refreshed automatically after withdrawing a task, bug, or issue. Status indicator on a Story shape in the scrum board is not changed when story is updated from Pending-Verification to Complete. Release Notes 4

5 Note: To submit new issues or find out more about the known issues, go to My Support Portal on the PDN. Be sure to reference the Issue ID in your communication. Resolved Issues As with any software product, features occasionally do not behave as intended. Pegasystems is committed to a high standard of quality, and has implemented procedures and programs to detect and correct such issues in the product. The following is a list of issues that have been resolved in this release that are of most interest and likely to have the most impact on the Pegasystems user and developer community. ID US BUG BUG Description The user story status list was missing the Pending-Sizing status. Usability Issue: User Story ID was not showing on PMF dashboard worklist making it hard to distinguish between 2 similar tasks on your worklist. URL field in Pulse was limited to 64 characters. This has been increased to 512 characters. Framework Documentation The documents included with this release and available on the PDN are: Project Management Framework Installation Guide V7.1.1 Project Management Framework Upgrade Guide V7.1.1 Project Management Framework User Guide V7.1.1 Release Notes 5

6 Copyright 2014 Pegasystems Inc., Cambridge, MA All rights reserved. This document describes products and services of Pegasystems Inc. It may contain trade secrets and proprietary information. The document and product are protected by copyright and distributed under licenses restricting their use, copying distribution, or transmittal in any form without prior written authorization of Pegasystems Inc. This document is current as of the date of publication only. Changes in the document may be made from time to time at the discretion of Pegasystems. This document remains the property of Pegasystems and must be returned to it upon request. This document does not imply any commitment to offer or deliver the products or services described. This document may include references to Pegasystems product features that have not been licensed by your company. If you have questions about whether a particular capability is included in your installation, please consult your Pegasystems service consultant. For Pegasystems trademarks and registered trademarks, all rights reserved. Other brand or product names are trademarks of their respective holders. Although Pegasystems Inc. strives for accuracy in its publications, any publication may contain inaccuracies or typographical errors. This document or Help System could contain technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Pegasystems Inc. may make improvements and/or changes in the information described herein at any time. This document is the property of: Pegasystems Inc. One Rogers Street Cambridge, MA Phone: (617) Fax: (617) Project Management Framework Document: Release Notes Software Version: Updated: Release Notes 6