Agile Development with UeXceler

An agile development method for every development team
Plus agile and UX tools like user story, sprint, wireframe and more.

  1. User Stories  

    Requirements can emerge and change throughout a software project. While many of the traditional development methods suggest capturing all requirements upfront, user stories is proven to be an effective approach in capturing and managing the ever changing requirements throughout the whole project.

    Written by user (or customer team), user stories describe functionality that are needed by and valuable to the users. As an integral part of many agile development processes, user stories offer a convenient way in recording user requirements, without having to write any detailed requirement documents, or have any prior consideration of system behaviors.

    Enhancement

    • Follow user stories

      Monitor changes teammates made to a user story by following it.

    • Supported editing the description of user story with the Description pane

      Edit the description of user story via both the Description tab the the Description pane.

    User Stories
    • Support of the 3C's

      User story Cards that records the Conversation with stakeholders and the Confirmation items for user acceptance test.

    • Configurable user story statuses

      Configure the statuses (e.g. Todo, Pending, Confirming, etc) of user stories for progress monitoring.

    • Estimate the time spent on user stories  

      Estimate the time required to accomplish user stories. Keep good balance between workload and the amount of work to deliver.

      Enhancement

      • Supported filtering user stories based on the estimated members

        Now, you can configure the filter to show only the user stories that are responsible by certain members, by selecting the members who have an estimation on the user stories.

    • Changes logged

      Crystal clear log of changes made to user stories.

    • Add custom properties to user stories

      Found the default properties not enough? Just add the properties you need.

    • Categorize user stories with tags  

      Group and categorize user stories by adding tags.

  2. Use Cases - Business Goals Modeled

    User stories is great in managing requirements, but where do they come from? Without an effective way to identify and manage user stories, your team may end up developing features that are out of the system scope. UeXceler thereby introducing the use of use case in an agile development process, in managing user stories.

    Found by communicating with top-level business stakeholders, use cases are high level business goals to be achieved by the system. With use cases found, you can then identify the user stories for each the use case. The result is a software product that brings real business values to your customers.

    Use Cases - Business Goals Modeled
  3. Manage User Stories with Use Cases

    It's the use cases that drive a project, and user stories that drive the development activities. To manage user stories with use case ensures that the features to develop are all goal-driven and within the project scope.

    Manage User Stories with Use Cases
  4. Manage Work Items with Sprint

    Customer team and development team work together in selecting the user stories to be accomplished in a specific time-period, known as sprint. You can manage the user stories in a sprint, assign team member to stories as well as to re-assign stories between members.

    Manage Work Items with Sprint
  5. Kanban Board

    Kanban Board is one of the most popular agile tool that helps scrum teams visualize the progress of a sprint. A Kanban Board presents and arranges user stories in a sprint in multiple columns of statuses (i.e. pending, todo, discussing, developing, confirming and finished), allowing scrum team to see the progress of a sprint easily. Besides progress monitoring, you can also move user stories between statuses (columns) with drag and drop.

    Kanban Board
  6. Access Anytime from Anywhere

    The web version of UeXceler lets you manage and browse requirements directly on the web (nothing to download or install), providing you with a more convenient way to record and clarify requirements when meeting stakeholders remotely. It also ensures the project team will stay up to date with any requirement changes.

    Access Anytime from Anywhere
  7. Business Process to User Stories Mapping

    Model business workflow with BPMN, and then identify user stories around the business activities. You can directly write user stories in a BPMN business process diagram, or any other diagram types.

    Business Process to User Stories Mapping
  8. User Story Scenarios*

    Describe the usage scenarios of user stories by writing down the interactions between user and system as steps. Stakeholder can read the steps and tell whether the steps are what he/she prefer.

    User Story Scenarios
    • Multiple scenarios

      Describe the different possible flows of a user story.

    • If-then-else

      Use conditional and loop statements like if-then-else and for-each in the flow.

    • Sequence diagram generation

      Visualize the interaction with UML sequence diagram.

    • Activity diagram generation

      Visualize the flow of steps with UML activity diagram.

  9. Link Scenario to Wireframe*

    A picture is worth a thousand words. By attaching wireframes to the steps of a user story scenario, the stakeholders will have a clear picture of how the system will work, which allows them to give early feedback on features to be developed.

  10. Storyboard in User Story*

    Use storyboards to show what the end user will see and interact with. With the help of storyboards, stakeholders can preview the system to develop, and to confirm that what you are going to build actually meets their needs.

    Storyboard in user story
  11. Engaging Storyboard Slideshow*

    Be a 'story teller'. Show your stakeholder a presentation of storyboard, and explain to them how the system will work by walking through the wireframes one by one.

    Engaging Storyboard Slideshow
  12. Keep the Design in User Story*

    Keep the design under user stories, and access them on-the-spot. Looking for the ERD as a reference in programming? Or the sequence diagram that represents the business logic to implement? You don't need a search because they are all under the user story that you are working on. Isn't it convenient?

    Keep the Design in User Story
  13. Requirement Specification*

    With just few mouse clicks, you can produce an up-to-date requirement specification that includes the details of use cases, user stories, storyboard, wireframe and other associated design artifacts.

    Requirement Specification

* Advanced agile development features are available in Visual Paradigm Professional and Enterprise only