Book a Demo

Author Topic: UML Profile for SCRUM ?  (Read 3946 times)

Guillaume

  • EA Practitioner
  • ***
  • Posts: 1405
  • Karma: +42/-2
    • View Profile
    • www.umlchannel.com
UML Profile for SCRUM ?
« on: March 09, 2010, 06:55:23 pm »
Hi,

I'm looking at using EA with an agile project involving SCRUM.
Does anyone know if a UML profile is available somewhere to support the SCRUM framework, e.g. product backlog, user stories, features, tasks...

Thanks,
Guillaume
Guillaume

Blog: www.umlchannel.com | Free utilities addin: www.eautils.com


Makulik

  • EA User
  • **
  • Posts: 400
  • Karma: +0/-0
    • View Profile
Re: UML Profile for SCRUM ?
« Reply #1 on: March 09, 2010, 08:41:52 pm »
Hmmm, isn't SCRUM more about development process organization (stand up meetings, CRC cards and other XP techniques)? Correct me if I'm wrong with that, I've never been using SCRUM.
I have no clue, what an UML profile should provide for this process in particular (except requirements analysis profiles, and those already exist).

Regards,
g.

Guillaume

  • EA Practitioner
  • ***
  • Posts: 1405
  • Karma: +42/-2
    • View Profile
    • www.umlchannel.com
Re: UML Profile for SCRUM ?
« Reply #2 on: March 09, 2010, 09:00:57 pm »
Hi

There is an approach in terms of generating sufficient (not too much) models/docs for SCRUM, introducing the concept of the following:
  • Spec user stories (e.g. scenarios under use cases)
  • Features
  • Tasks

Basically all is available under EA to do this, but a UML profile would be useful especially if it's been tried and tested
Hence, if a UML profile and possible base project structure is available; it'd be useful.

cheers
Guillaume

Blog: www.umlchannel.com | Free utilities addin: www.eautils.com


SPM

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: UML Profile for SCRUM ?
« Reply #3 on: April 01, 2010, 12:20:33 pm »
Hi,
We use EA in our Agile Scrum methodology and have created an EA feature called 'Story'. We start with a Use Case and link stories to it. In Jira /Greenhopper a Jira feature = a use case and stories can then be managed/grouped much more easily.  You end up with many stories, associated tasks and defects in Greenhopper during the course of building a system however we need the clear EA models (which we tidy up at the end of each sprint) for traceability, maintenance and project communication.

•Create a new UML Profile that contains a Stereotype called ‘Story’.
•Construct the Story Stereotype by extending the Feature Element.
•Add an additional attribute to the Story Stereotype to enable us to record the Description, utilise the Notes field within the Story Stereotype to record the Steps to Demonstrate.
•Load that new UML Profile into any EA project whenever you wish to utilise the Story Stereotype.
Hope that helps