INDEX:
- What is Agile and what could Hive borrow from it
- Leave your feedback for the first year of life of Hive!
INTRO:
( this is techy stuff ..if you just want to leave your feedback, follow the instructions at the end of the post.. )I have been working in Agile teams for quite a few years now.
I have used Scrum, Kanban, a variant of RUP (Rational Unified Process) and Safe (Scaled Agile FramEwork - ie. Scrum on steroids for big teams).
I even led these Agile ceremonies in a team that I was leading as a Tech Lead for a customer (I work for a private IT consultancy). That's usually not my role but the client still had to hire a Scrum Master / Product Owner that would perform this duty so for a few months I wore multiple hats.
[small digression - back when I started working for that client, they were just a startup with 12 devs coding in a coworking space. Now 2 years later they have hundreds of employees, an office with a view of Manhattan's skyline and they are official partners with CBS sports, NBA and NFL. They recently got purchased for the modest price of 4 billion dollars!]
SCRUM
Summary taken from https://resources.scrumalliance.org/Article/quick-guide-things-scrum 👇👇👇
Overview: What is Scrum?
Scrum is a lightweight yet incredibly powerful set of values, principles and practices.
Scrum relies on cross-functional teams to deliver products and services in short cycles, enabling:
- Fast feedback
- Continuous improvement
- Rapid adaptation to change
- Accelerated delivery
Understanding the Scrum Flow
At its heart, Scrum works by breaking large products and services into small pieces that can be completed (and potentially released) by a cross-functional team in a short timeframe.
Scrum teams inspect each batch of functionality as it is completed and then adapt what will be created next based on learning and feedback, minimizing risk and reducing waste. This cycle repeats until the full product or service is delivered—one that meets customer needs because the business has the opportunity to adjust the fit at the end of each timeframe.
The Agile methodology is not for every team but I think that Hive could benefit from some of these practices. These are the ceremonies used in Scrum:
Standup meeting: every morning the devs of every team (each composed by 6/10 people - usually mostly Devs, one Product Owner and one or more Testers) go around in a circle saying what they worked on the day before, what they plan on working on during the day and they tell the team if they have any blockers or need help on something. These updates are kept short and any topic that needs further discussion is continued offline right after the meeting with only the interested parties (aka parking-lot meeting).
Spring planning: each Scrum team discuss the tasks they will work on in the following 2 weeks (typical duration of a development "Sprint"). Tickets are estimated in their complexity and the top priority tickets added to the Sprint based on the realistic capacity of the team.
Backlog refinement: the team analyzes the tickets that they have in their team's Product Backlog (features, bugs, tech debt). They briefly discuss possible solutions & concerns and try to give a first estimate of the work required for each ticket. New tickets may be created as well by the Product Owner based on business priorities and by devs if for example critical tech debt needs to be addressed and the PO sees value in it.
Show & Tell: each development team demo-es to the attendees (other devs, Product people, stakeholders, etc) what they got DONE during the last sprint - ie. developed, tested, got signed off and ideally shipped to a certification of pre-production environment.
Retrospective meeting (aka Post Mortem): the team discuss what went well in the past sprint and what instead could be improved in the future, keeping in mind that everyone did their best and a solution should be found together as a team. A smaller group (eg. Product Owners, Product Lead, Tech Leads, CTO, QA lead, etc) may then also meet for a Scrum of Scrums meeting to discuss retrospective notes from all the teams.
What could the Hive community borrow from Scrum?
I think that Show & Tells for the community could be organized (every 3/6 months?) to showcase what the various Hive ecosystem projects achieved and to get early feedback from the community. This could be done in AltspaceVR - maybe @themarkymark could help organizing them since according to his presentation during the HiveFest he has been doing some Hive meetups there already?
I think that regular Retrospective "meetings" for the Hive community would be beneficial both for the end users and for the developers working on Hive projects.
So.. here is an attempt to do our first..
RETROSPECTIVE MEETING FOR HIVE
Retrospective for the 1st year of life of Hive
Please write in the comments section [under my own comment saying "POST YOUR FEEDBACK HERE"] a reply that contains the following 3 points:
- 1. What you think went well +
- 2. What you think went wrong or should be improved +
- 3. Shout outs (feel free to tag any users that you think should know that they are doing a great job!)
For every item that you think went wrong... if you only want to vent that's fine, but if you think that there's something concrete that could be done to improve it.. share your thoughts!
How? Add an ACTION ITEM right next or below the item that you think needs some improvement. Propose practical solutions for anything negative that you think happened/is happening on Hive.
Tag any user(s) that you think should own the action item. Hopefully they will reply and decide to indeed own that task, or they may recommend someone else.
Example:
1. Went well:
- Got rid of Steemit Inc!!
2. Went wrong:
- The community is not quick enough when it comes to reacting to phishing -- ACTION ITEM: @keys-defender to keep automating as much as possible, humans are slow! ��
3. Shout outs:
- Good job to @guiltyparties and @pfunk for always being on top of any abuse going on on Hive and for constantly finding ways to help Hive grow!
Or if you prefer to use a different format for your feedback, reply to these 3 questions:
I - What should the Hive community/devs STOP doing?
II - What should the Hive community/devs CONTINUE doing (because it works)?
III - What should the Hive community/devs START doing?
Categories (for further discussions)
If you are willing to share more detailed feedback or suggestions, please use an existing category in the comments section of this post, or create a new category altogether.
PS. You can also leave your feedback directly under one of the categories.
Example:
[this post]
-- comments --
- (@gaottantacinque's comment) <h1>categories</h1>
- user1: <h4>Marketing</h4>
- reply from user1: I think that we should contact SomeGuy youtuber for better exposure
- reply from user2: Have we thought about using Brave ads?
- user2: <h4>DHF</h4>
- reply from user3: some projects should post more updates, they almost seem inactive.
I will keep editing this post to reference all the categories added in the comments section. In this way you'll have a direct link to a category and messages won't get hidden by the UI if a thread has too many replies.
Categories:
- Frontends
- Games
- Tribes
- Security
- Onboarding
- LEO / CUB
- Documentation for developers
- Price
- Communities
- ...
If this goes well and we get useful feedback from the community about: Hive, the projects of the Hive ecosystem and the core development team, I think it would be a good idea to do a retrospective meeting post EVERY QUARTER (ie. the next one would be at the end of June).
Take care,
@gaottantacinque (@keys-defender)