Howdy,
Most of us developers have been in heavy feature mode the past two months
and as such have had to take an idea and turn it into a user facing
feature. From these experiences, a rough workflow has emerged that each
feature has gone through. I'd like to share the distillation of this for
exposure and discussion:
*Steps*
1. Identify the over arching story (e.g. Better Errata Management)
2. Brainstorm and write up initial set of user stories and requirements
with respect to the UI, API and CLI (e.g.
http://pad-katello.rhcloud.com/p/errata-management-stories)
3. Send a write-up out to the users list for feedback
4. Refine user stories based on feedback
5. Groom the user stories using planning poker with team (
http://www.planningpoker.com/)
6. Add design artifacts to wiki (e.g.
http://projects.theforeman.org/projects/katello/wiki/CapsuleCommunication)
6. Create a Redmine tracker for the over-arching story (e.g.
http://projects.theforeman.org/issues/7125)
7. Add stories to Redmine that come out of grooming including story points
8. Set all stories to block the Tracker, optionally set stories that block
each other
9. If there are new UI components, consider contacting Kyle to discuss UX,
add mock-ups to design wiki
10. Assign stories to sprint based on capacity and number of engineers
working on that feature
11. Complete stories
12. Demo stories completed during sprint demo
13. Gather feedback from demo and generate any new stories or bugs that
need to be created
14. Repeat steps 10-13 until all stories blockiing Tracker are complete
15. Write up documentation about new feature
Eric
Sounds like a logical way of working. I'd like to note that there should
be focus on terminology. For me it's unclear what a capsule exactly is,
but I very much know I'd want to separate my clients from my
foreman/katello server. Deducing from the context a capsule is a smart
proxy in foreman terms?
···
On Thu, Oct 30, 2014 at 10:19:20AM -0400, Eric D Helms wrote: > Howdy, > > Most of us developers have been in heavy feature mode the past two months > and as such have had to take an idea and turn it into a user facing > feature. From these experiences, a rough workflow has emerged that each > feature has gone through. I'd like to share the distillation of this for > exposure and discussion: > > *Steps* > 1. Identify the over arching story (e.g. Better Errata Management) > 2. Brainstorm and write up initial set of user stories and requirements > with respect to the UI, API and CLI (e.g. > http://pad-katello.rhcloud.com/p/errata-management-stories) > 3. Send a write-up out to the users list for feedback > 4. Refine user stories based on feedback > 5. Groom the user stories using planning poker with team ( > http://www.planningpoker.com/) > 6. Add design artifacts to wiki (e.g. > http://projects.theforeman.org/projects/katello/wiki/CapsuleCommunication) > 6. Create a Redmine tracker for the over-arching story (e.g. > http://projects.theforeman.org/issues/7125) > 7. Add stories to Redmine that come out of grooming including story points > 8. Set all stories to block the Tracker, optionally set stories that block > each other > 9. If there are new UI components, consider contacting Kyle to discuss UX, > add mock-ups to design wiki > 10. Assign stories to sprint based on capacity and number of engineers > working on that feature > 11. Complete stories > 12. Demo stories completed during sprint demo > 13. Gather feedback from demo and generate any new stories or bugs that > need to be created > 14. Repeat steps 10-13 until all stories blockiing Tracker are complete > 15. Write up documentation about new feature> 3. Send a write-up out to the users list for feedback
- Put the write-up in our wiki in this form:
http://projects.theforeman.org/projects/foreman/wiki/PXE_Booting_UEFI
and send the link to the lists. Continue updating the wiki (status,
elaboration…)
···
-- Later, Lukas #lzap Zapletal>> 3. Send a write-up out to the users list for feedback
>
> 3. Put the write-up in our wiki in this form:
>
> PXE Booting UEFI - Foreman
Maybe stick a template on a page for quick grab?
···
On Fri, Oct 31, 2014 at 7:44 AM, Lukas Zapletal wrote:and send the link to the lists. Continue updating the wiki (status,
elaboration…)–
Later,
Lukas #lzap Zapletal–
You received this message because you are subscribed to the Google Groups “foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> > PXE Booting UEFI - Foreman
>
> Maybe stick a template on a page for quick grab?
Done:
http://projects.theforeman.org/projects/foreman/wiki/Sprint_Feature_Template
LZ