Alanna Risse

AW Awards
https://www.awwwards.com/websites/bootstrap/

bootstrap Expo
http://expo.getbootstrap.com/

Bootstrap Bay
https://bootstrapbay.com/blog/built-with-bootstrap/

Color Lib – Bootstrap portfolios
https://colorlib.com/wp/bootstrap-portfolio-website-templates/

Handy Bootstrap pieces and parts on tutorialize
https://tutorialzine.com/2015/06/12-time-saving-bootstrap-examples

Flex Order in bootstrap
https://getbootstrap.com/docs/4.0/utilities/flex/

From Wikipedia: Crab Mentality:
“Crab mentality, sometimes referred to as crabs in the bucket (also barrel, basket or pot), is a way of thinking best described by the phrase, “if I can’t have it, neither can you.” The metaphor refers to a common pattern of behavior seen in a group of crabs when they are trapped in a bucket: Their focus is on saving oneself rather than willing to cooperate to save the entire group. Individually, any given healthy crab could easily escape, but when grouped with others, any individual’s escape will be hindered by others. They will grab at each other in a futile “king of the hill” fight for survival, which eventually ensures their collective demise.

The analogy in human behavior is claimed to be that members of a group will attempt to negate or diminish the importance of any member who excels far more than other members or achieves success that overshadows others’, out of envy, spite, conspiracy or competitive feelings.”

Also from Wikipedia: Allegory of Long Spoons:
“The allegory of the long spoons is a parable that shows the difference between heaven and hell by means of people forced to eat with long spoons. It is attributed to Rabbi Haim of Romshishok, as well as other sources.

In hell the people are unable to lift food to their mouths using such unwieldy cutlery, and are starving. In heaven, the diners feed one another across the table and are sated. The story can encourage people to be kind to each other. There are various interpretations of the fable including its use in sermons and in advice to lonely people.”

I’m doing some research on how to run productive sprint retrospectives.

Mountain Goat Software has a good structure that breaks down into how to encourage good habits:

Start: What needs to be added to the team’s habits
Stop: What needs to be changed or removeed
Continue: What working but needs to continue in order to become a habit.

Once something becomes adopted as a habit, it drops off the list. Otherwise the list would grow.
The key is, keep it short, keep feelings out of it. I also like that in each sprint retrospective, there is a sheet of paper with last week’s retrospective points so the team can see them. They don’t need to be discussed but having them as a reference is helpful/

I’ve had other weekly retrospectives that were like this:
Each person takes a turn listing:
Round One: 3 things that worked
Round Two: 3 things that could be improved upon
Round Three: Any blockages
The meeting ends with a quick list of what’s happening the following week, plus a shout out to someone or something exceptional that happened that week.

This style works well on teams with new employees because it forces everyone to become part of the discussion from their very first week. I like tat the feedback is given in rounds instead of having the first person go through the pluses and minuses before moving on. It allows for time to think about your own list and modify it.

Most importantly, I think, is to get the retrospective done fast, record what’s been discussed, and move on. We’re smart humans, a quick check in is usually enough to plant a seed for future improvements, or when necessary, a follow up conversation off-line.