= Questions/Requested Information
Many of us working in open source communities are used to issue trackers of various sorts. We use them for many different things: user feedback (bugs, RFEs), tracking new features, ideas, etc. This results in 10s or 100s of issues that might be hard to navigate through, because they are so different, yet mixed together.
I feel there is a big difference between user feedback (something anyone can submit), a key feature to be developed (something the core team defines based on user needs), and a unit of work (an actionable item leading to a new feature being developed).
Could we adopt some of the existing agile principles to solve this problem? Can we do it in a way suitable for open source communities where people often contribute irregularly, in their spare time?
I believe we can! And I will demonstrate how we use Kanban for the Antora for Docs project, bringing a new documentation site to Fedora. Using this, we’ve been able to:
I believe adopting similar principles could bring some additional clarity to your open source project — mostly about about it’s future, user feedback, upcoming features, and the work that needs to be done, potentially scaling your community.
Anyone curious about agile, project management, communication, and similar topics. I would appreciate having some professionals in this area (I’m a software engineer myself, so I might be completely wrong) :-)
Is this a … (Delete all that DO NOT apply) * Talk of 30 minutes
Anything else we need to know? This could be room setup, A/V needs, etc. If you have private concerns, please email them to flock-admin@fedoraproject.org.
Who are you? * Name: Adam Samalik * FAS ID: asamalik
+1
Depending on how final scheduling works out, I'd love to attend this session if accepted.
Metadata Update from @bex: - Issue tagged with: Talk In Consideration
Metadata Update from @bex: - Issue untagged with: Talk In Consideration - Issue tagged with: Talk Accepted
Metadata Update from @bex: - Issue close_status updated to: Talk Scheduled - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.