Member since 2 years
Specialises In (based on submitted proposals)
I am working as Manager Operations with Ucreate India HQ.
Code reviews - a hidden gem to save time, increase team happiness and improve knowledge sharingNeeraj AgarwalManager OperationsUcreate it
schedule 1 year agoSold Out!
Most of agile conferences talks focus on "soft side" of being agile. We discuss process guidelines, Scrum Masters responsibilities, team building exercises and servant leadership ideas. In our quest to be agile we sometimes forget about developers and technical members of our teams, their tools, processes and way of thinking. Aspects like code reviews, TDD, CI, pair programming are hard for us to understand and justify spending time on them. We should not forget that at the end of the day great products we create needs great code to run.
All organisations whether startups or large established are products and services using Agile guidelines. But most agile transformations focus on SM and PMs forgetting about developers and their challenges. It's a tough life being a full stack developer these days. They have to keep innovating & adapting latest trends in technology. PO & PM always want changes or ideas to incorporate ASAP, Moreover every line of code is exposed being pushed code to live multiple times a day.
Constant Environment change, New languages and their regular updates, Huge legacy apps, Constant request from business to do more in new cutting edge has increased complexity in writing code. Code that is difficult to understand, hard to modify and challenging to extend is hazardous to developers, users and organizations. So what measures can be used to prove the code quality and the approach for improving the quality of the code base.
“Code review” can be a handy tool catering the developers in real time to groom their skills while keep them focused on the agile process.
Code review actually empowers agility by improving product and code quality and eliminates defects early when they are least expensive to fix. Code review process let developers think of new ideas how to write better code every time. Moreover, when working on project no-one is the only person who knows a specific part of the code base. Code review facilitate knowledge sharing of the code base across the team. Agile teams can realize huge benefits because work is decentralized across the team.
Team journey from I to WeNeeraj AgarwalManager OperationsUcreate it
schedule 2 years agoSold Out!
I have been working as a Scrum Master with a team for a few months. In one of the releases we encountered a bug in our production release. Technically it was a small check missing, but when the team started discussing it then everybody was pointing at other team members as a source of issue. No one was willing to accept responsibility or creatively consider what went wrong and how to stop this from happening again. It was all about finding someone to blame. This situation changed my focus to explore the aspects of teamwork from the perspective of blame and to look into best possible ways to build a team that never use blame to find out solutions to team challenges.
I will try to share a few examples of how our organisation with #noblame culture tries to behave in moments of crisis and how we never considered blame to be an option or a solution.
I am also very confident that this problem is present in more than just our organisation and it impacts our ability to deliver great value to our customers and build great teams.
As we all know our agile teams should be accountable to each other first but i believe many teams and Scrum Masters often confuse accountability with blame. There is usually an underlying set of issues with people using blame as a solution to their problems. For one it feels good, not to be responsible for team problems. Usually there could be a deeper reasons why a person would play a blame game. Those reason vary from unhappy either in personal or professional life or trying to protect herself due to insecurity. Also in modern society people are so much stressed and obsessed with their desire to be successful they feel happy by blaming others they remove spotlight and pressure from themselves. All those behaviours are very dangerous and impact the team ability to deliver value to users.
During the session we will discuss how we try to create no blame culture, what we do and how you can apply those lessons in your context. I will share some practical examples, theory to back them up and aspects that worked for us. I will also share some failures and mistakes we made on our way.
No more submissions exist.
No more submissions exist.