COmanage Developers List

[Scott Koranda <>]

Hi,

Perhaps we can talk about these on our next dev call?

Thanks,

Scott


---------- Forwarded message ----------
From: Mike Manske 
<>
Date: Thu, Mar 5, 2015 at 3:28 AM
Subject: From last converstation
To: Scott Koranda 
<>,
 Warren Anderson
<>


Scott - just wanted to reiterate the points from our last conversation.

I had a couple ideas to help development and deployment that should
have quick payoff.  I would be very happy to help to whatever extent
is needed (Please, be me like a rented mule :) )

1 - use the Jira plugin for agile, not so much for scheduling but for
***managing user stories (aka requirements)***.  Benefits:

- Each story starts very high level - a sentence or two and grows more
detailed as they evolve, and may eventually include sketches, process
steps, flow diagrams
- Traceable team collaboration
- Traceability from requirement to change (defect or enhancement).
Helpful for things like seeing true cost of a piece of work.
- Can be basis of user docs

2 - Change procedure on defect resolution. Specifically, require
reporter to resolve a defect. This will promote agreement between
reporter and developer. It will also improve quality of Jira entries.
Many of us, including me, have been guilty of one sentence (or less)
Jira entries.

This will require agreement on status definition and process. The
developer will need to communicate 'code complete' and location of new
code, and the reporter will need to communicate 'fix validated' (or
not). etc.





--
Michael A. Manske
Leonard E. Parker Center for Gravitation, Cosmology and Astrophysics
University of Wisconsin - Milwaukee
Physics Building, 452
Phone: 414.335.6366