Discussion of the scope for the OSP 2.4 release. Consider that the release is planned for the April 2007 timeframe and the code freeze for the release is on March 15th. List items that you believe are important to include in the upcoming release. Ultimately the scope will be determined by the folks who commit to work on the 2.4 project, the resources available, and the time constraints. Also see the /wiki/spaces/REQ/pages/13648396425
Draft
...
- One specific example is to be able to complete forms and add files when creating a portfolio, rather than adding everything in Resources first.
- Also, add ability to upload files/documents in the comments area of a portfolio.
...
High Level Scope
Each of the items below represents a high-level scope item. These are intended to frame the release and focus our efforts on elaborating requirements that fall into scope, and postponing work on requirements that fall outside the scope. Once requirements are complete, the set of agreed upon requirements will be the detailed scope for the release.
UI rework/refinement. Focus on making the user experience more integrated and cohesive. This will involve assessing current user workflow's, reducing clicks, potentially reducing tools, increasing UI consistency between tools, language consistency, etc.
Documentation.
Sample data structures.
Reports.
Forward compatibility.
Integration with Goal Management Tool.
Increase ability to edit data structures once created.
Create "Builders" for the hard to create xsd, xsl, css, xhtml files
...
- Provide Documentation for Authoring xsd, xsl, css, xhtml files (unless we have builders allowing end-users to create these)
- Identify 3 key types for portfolios and provide documentation on workflows for creating each and sample data structures
- Rethink immutable design of published items such as forms, matrices, wizards etc. When does it make sense to allow changes to published data structures. (ie) Should it be possible to add on to a matrix once it's already in use? (see 4th bullet point above)
- Provide better differentiation between user's portfolio experience kept in My Workspace and user's interaction created in a group space.Site centric vs User centric portfolio experience.
- Add notification for published data structures (ie you have 1 new wizard assignment)
- Add notification for submitted data structures (ie you have 1 new wizard submission)
- Make Wizards, Matrices and Forms goal aware
...
| title | General Comment |
|---|
...
.