Alley’s core company values of quality, transparency and accountability closely align with the values of Scrum and, more broadly, the principles of agile software development. However, recent events have led us to consider how the practice of Scrum also supports our community values – radical candor, psychological safety, asynchronous communication, diversity, and inclusion.
As more and more companies go remote, it will become increasingly more common to provide code samples with résumés. How should you select your code samples? What should you do to prepare them? Here are five things I look for when reviewing code samples.
For all of us to play the same song, everyone needs to have a good understanding of Scrum. Scrum certification is the way to ensure that that happens.
Working remotely means we’ve had to be intentional about ensuring designers canconnect, talk shop, and spur each other on creatively. Here’s how.
In this article, we’ll go through some of the reasons why you should increase your productivity with pair coding – working towards a solution with one other person – and swarming – working towards a solution with multiple people.
At Alley, we’ve built a culture of collaboration where designers and developers see each other as true partners instead of adversaries.
The myths of web design must be changed along with developments in bridging the designer/developer divide, new tools, and more.
Being a scrum master, I often worry if velocity looms too large for me. From project forecasting to sprint planning to team retrospectives, velocity metrics are up in my grill more than bratwurst at a Green Bay Packers tailgate. Even from a “book learnin’” standpoint, velocity is front and center: “The Scrum Master is accountable for the Velocity … of the Team.” That big V Velocity is really intimidating! But does velocity warrant such verbal (and mental) emphasis?