[Maintainable Podcast] Building a Technical Leadership Career Around Teaching

I was honored to talk with Robby Russell (@robbyrussell) about technical leadership and maintainable code. It was my very first podcast. Hope the content is helpful: Magda Miu: Building a Technical Leadership Career Around Teaching.

Continue reading “[Maintainable Podcast] Building a Technical Leadership Career Around Teaching”

7 Steps to Technical Leadership

I work as a Technical Leader since 2016. During these years the most important lesson I learned is that as a servant leader my main focus should be my team because everything it’s about them, it’s not about me. Actually, my main responsibility is to set up my team members for success.

The success of a product is a team effort and my role is to build, train, and lead engineers. Awesome teams build awesome products. In order to achieve this objective, it’s necessary to combine tech skills with people skills.

Continue reading “7 Steps to Technical Leadership”

About 2019

This year was about new opportunities, new job, new team, GDE life, Agile Squads, Android, WorkManager, Kotlin, mentoring, courses and speaking at conferences and events like: Android Makers Paris, Workshop at Politehnica University Bucharest, Android Course at Google Atelierul Digital, DevTalks Bucharest, Droidcon Cluj-Napoca, Codecamp Bucharest, Workshop at SISC ASE, DevFest Bucharest, DevFest Craiova, Kotlin Everywhere Cluj-Napoca. ✨ ✨ ✨

Continue reading “About 2019”

Artifacts in Scrum

As I promised in my previous articles, Roles in Scrum and Events in Scrum, I’m following up with a related article on Artifacts in Scrum.

In Scrum there are three tangible deliverables, called artifacts. These artifacts consist of the requirements for the overall project, the requirements for each piece of the project, and the project itself.agile-process-overview_klein-1 Continue reading “Artifacts in Scrum”

Roles in Scrum

This article will focus on the Roles in Scrum and it will be followed by another two which will contain details about the Events in Scrum and Artifacts in Scrum.

Scrum is an Agile framework used to develop projects and is based on the concept of “KISS” (i.e. Keep it Simple Stupid). The first mention of this technique can be found in 1986, by Hirotaka Takeuchi and Ikujiro Nonaka and then it was used for commercial product development. The first official document defining Scrum was presented in 1995 and was written by Jeff Sutherland and Ken Schwaber.

The name “Scrum” is a term from rugby, and it’s used as a metaphor to reflect the degree of cooperation needed to succeed. So scrum is a Team pack in rugby where everyone in the pack acts together to move the ball down the field.

Continue reading “Roles in Scrum”