Retrospective for the first year of Hive - leave your feedback !!

avatar
(Edited)








INDEX:

  1. What is Agile and what could Hive borrow from it

  2. 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:

src

  • 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?

src

 

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:

Please before creating a new category check if it already exists, let's avoid dupes! 😎 👍

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).

Please reblog so that as many users as possible will partecipate to this survey !



Take care,
@gaottantacinque (@keys-defender)

hive birthday hivedev technology neoxian palnet
0
0
0.000
41 comments
avatar
(Edited)

POST YOUR FEEDBACK HERE   👇


 

0
0
0.000
Reply
avatar
(Edited)

1. Went well:

  • Got rid of Steemit Inc!!
  • Development continued at a fast pace
  • Communities growth
  • Hive Fest

2. Went wrong:

  • Some good efforts in this space but still not enough marketing - ACTION ITEM: @guiltyparties and @lordbutterfly to keep working on it and achieve great results!
  • 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! 🤖
  • PS. Not enough engagement on posts   :( - ACTION ITEM: create @thank-you-for-engaging(?) bot that automatically upvotes comments longer than X words on posts with less than Y comments - @gaottantacinque

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!
0
0
0.000
Reply
avatar
  1. Went well:
  • Got rid of Steemit Inc!!
  • active community with a desire to grow
  • New developers have approached our chain
  1. Went wrong:
  • Proxy system, witness votes, exchange of votes
  1. Shout outs:
  • To the whole community that makes Hive HIVE!
0
0
0.000
Reply
avatar
(Edited)

Thanks for your feedback @phage93. Could you please elaborate on the negative points?

0
0
0.000
Reply
avatar
(Edited)

Of course, currently the proxy system is the most used both from the point of view of the vote on the witness and as regards the path of voting trails. This is because many users and old investors, have moved away from the platform drawing only the benefits of automating as much as possible their actions on the chain. This involves a large amount of voting in the hands of a few and the impossibility of having a fair reward distribution.
I’ll leave you a screen of the various proxies:

proxy.PNG

tnx to arcange https://hive.arcange.eu/witnesses/

As for the exchange vote also it is present both in the witness landscape and in that of the blog. Needless to mention who and how, through hive.arcange.eu and other tools, you will see many interesting things.
there is the bernie' witness still active(innerhive), and five witnesses under the top 50 who haven’t updated the price feed in years, are still all vote given by the accounts on the steem chain, which have been inactive for years.

0
0
0.000
Reply
avatar

Thank you for your detailed explanation.

Do you envision any possible solutions?
Eg.

  • a proposal to make inactive witnesses lose their rank.
  • have proxies only accept X users and with a good balance of age of the account and reputation. These could be automatically and periodically rotated as well.
  • automated warnings added to frontends for users that constantly circle jerk?
0
0
0.000
Reply
avatar

As for the part of the witnesses, on a post of @blocktrades a few weeks ago, it was said that there would be some sort of cleaning up on the old votes given, ( older than a year I seem to remember) But I don't know if the speech was more touched or carried forward, as you can imagine would mean a nice nuisance, for those who are there to do farming without doing anything...

(surely a moderate view where there can only be x proxies or only a value of x would be a better compromise)

Some alerts could be inserted why not ... on hive.blog there would be plenty of nice things to implement ... consider that practically nothing has changed between now and 5 years, only the community part ...

0
0
0.000
Reply
avatar

The code for expiration of old votes has been completed and will be included in hardfork 25.

0
0
0.000
Reply
avatar
(Edited)

Right, I think that only @quochuy has actively been working on it. He added a few nice features.
But yeh peakd did the flippening a few months back.

0
0
0.000
Reply
avatar

I'm slowly adding more features introduced by Peakd and Ecency. More can also be done if the backend (Hivemind or API) is also updated.

0
0
0.000
Reply
avatar
  1. What you think went well

a. managed to change the chain id
b. successful migration of most of the community

  1. What you think went wrong or should be improved

a. Have not managed to fully close attack vector --ACTION ITEM: Reduce witness votes per user to 8 (game theory), or have witness vote power be divisible by number of votes cast.

b. EIP reward curve still stupid -- ACTION ITEM: put it back to linear and let stake reward comments or posts however they want.

  1. Shout outs (feel free to tag any users that you think should know that they are doing a great job!)

Shout outs to @taskmanager, @raymondspeaks, @josephsavage, @rycharde, @gerber and @khaleelkazi for working diligently on great projects!

0
0
0.000
Reply
avatar
(Edited)

Categories (for further discussions)   👇


 

0
0
0.000
Reply
avatar
(Edited)

Frontends

0
0
0.000
Reply
avatar
  1. Went well:
    • PeakD, Ecency, Dapplr, etc. rose from the splitting mess.
    • Continual developments on the said front ends are still happening.
  2. Went wrong:
    • Some community features are broken, but that's more on the Hivemind end, I believe.
    • Results of voting have delays now.
  3. Shout outs:
0
0
0.000
Reply
avatar
  1. Went well:
  • PeakD, Ecency, leofinance, nftshowroom
  1. Went wrong:
  • synchronization with some nodes is difficult, I do not know who is to blame, but it is very cumbersome to change the nodes by hand for a normal user.
  1. Shout outs:
0
0
0.000
Reply
avatar

I agree on the nodes issue. For instance on peakd when you get a 404 page due to node issues, it lets you choose the node to use but the url parameter (url?node=chosen-node) does not follow you around. I know that you can specify a different node in the settings but most of the times I only want to temporarily switch to a different node (I know, I’m lazy). That should be an easy fix though - cc: @asgarth @jarvie

0
0
0.000
Reply
avatar

Games

0
0
0.000
Reply
avatar
  1. Went well:
  2. Went wrong:
    • The split from Steem really threw a monkey wrench into the flow of things.
  3. Shout outs:

I'm sure there are others, but this is the best I can think of on the top of my head.

0
0
0.000
Reply
avatar

Tribes

0
0
0.000
Reply
avatar

Sad there is no section for communities since this is a Hive recap and it's where peakd has seen the biggest growth on our site. But I guess you'll get some scot-bot users to comment here about their tribe.

0
0
0.000
Reply
avatar
(Edited)

As written in the post, these Categories were only added to get the ball rolling and I expected the users to add many more. I will add it myself then 👍

0
0
0.000
Reply
avatar

Do you think there is anything positive about tribes?

And do you have a suggestion on how the issue you mentioned could be mitigated?

0
0
0.000
Reply
avatar
(Edited)

@jarvie Eg. Do you think it would be feasible to have bots request an api key that has to be approved by 1 or 2 top 40 witnesses and revoked if abused?

0
0
0.000
Reply
avatar
  1. Went well:
    • Most major tribes migrated over to Hive
    • One of them excelled: LeoFinance
    • Cool utilities such as @hiveonboard debuted thanks to events like Hive Hackathon, which was partially sponsored by the STEMGeeks tribe.
  2. Went wrong:
    • Some tribes got devastated by JSun's takeover (i.e. SteemAce, Upfundme, Photo); they basically ceased to function the way they did before.
    • Other tribes lost the momentum due to the chaos of the takeover (i.e. CreativeCoin)
  3. Shout outs:
0
0
0.000
Reply
avatar

Security

0
0
0.000
Reply
avatar
(Edited)
  • unmaintained apps with known and unfixed security issues should be removed from the wall of featured Hive apps
0
0
0.000
Reply
avatar

Onboarding

0
0
0.000
Reply
avatar

WENT WELL
Hiveonboarding made it incredibly simple and fast to get keys.
PeakD and others integrated it

NOT GOOD YET
New users still don't know how to use those keys effectively

SHOUT OUT
@roomservice @cardboard

0
0
0.000
Reply
avatar

Documentation for developers

0
0
0.000
Reply
avatar

If we're talking about the whole year, on the topic of documentation ...

  1. Went well:
    • The team did an excellent job setting up the initial space for devportal: https://developers.hive.io/
    • Communicated the goals for devportal and executed branding transition.
  2. Went wrong:
  3. Shout outs:
0
0
0.000
Reply
avatar

Price

0
0
0.000
Reply
avatar

WENT WELL
We spent the year focusing on projects and products and tying them to things other than price... so we could have a foundation for more than a momentary boom.

WENT WRONG
We saw that many many people came only for the money and thus we had many many people leave because that was what they were sold.

0
0
0.000
Reply