Dev Leadership Summit
Wednesday, June 17, 2020
From a small startup to a fortune 500 company, it has been an amazing journey and a new lesson learned at each step. Join me, a program manager at Microsoft, as we take a walk down memory lane to learn about all the ways you should (or should not) build your local and global developer communities. In this session, we will cover the three pillars of success to help you organize events, connect with speakers, and create everlasting engagement. Additionally, in this new virtual era, discover how to bring your events online to the exciting world of live-stream.
Empathy is what will define the great companies of the future that create products that truly fulfill the needs of our diverse world. These companies will be made up of diverse populations across gender, race and ethnicity designing and building the technology of the future. Engineering with empathy can not only create teams that work well together, but will produce better products. Empathy is a skill that can not only be learned, but is one that we can improve on with regular practice. Engineers don't tend to think about empathy as an important part of building software, but I want to change that mentality. You will learn how empathy can be applied in practical ways to every day engineering activities like code reviews, project planning, and team meetings. I will also share how you can lead with empathy to take your engineering leadership skills to the next level.
Nowadays, great rivalry exists in software world. Everyone tries to reduce time to market, cost and increase the coverage and quality as much as possible. In this manner, managers try to minimize inner costs. They investigate the efficiency of each process. QA teams and activities are under investigation as well:
- Are we spending too much money for QA: What are they doing? Is it worth?
- Are they successful?
How can you understand if your QA team is successful? In this presentation, most useful metrics to manage, track and evaluate QA teams & processes are discussed. Bad metrics (giving no idea about success) are also presented. For instance, being concentrated on only test case numbers can lead us to wrong perceptions. Apart from numbers, quality and coverage are of great importance in terms of maturity of testing processes. Not to overcome other weaknesses, I will discuss what maturity metrics should be followed comprehensively. (without being stuck only on test case numbers)
All claims are supported with real-life experiences by people, who have been trying to manage QA activities in DevOps environment. Finally, our aim is to find ways to achieve convincing our managers and ourselves as well for the necessity of QA activities and teams.
After going over metrics which demonstrates the progress and quality of the product; we will all have a chance to compare how QA activities save money, time and prestige since potential bugs, which are likely to appear in Production environments are eliminated in early stages.
I will have a little code demonstration, in which we will collect data from Jira (using Jira API) & post them to CloudWatch to monitor them on graphs.
* Introduction: Metrics & Monitoring
* Activity: A little demo about what happens without progress check & monitoring
* Important QA Metrics
* Practical Case Study: Storing Metrics in Amazon CloudWatch: Collect Data from Jira & Post them to CloudWatch, Create Dashboard & monitor Graphs: All over Java code.
Talent optimization is how successful leaders make sure their business strategy is executed to get the intended results.
It empowers executives, managers, and individual contributors by providing:
- A method of aligning people practices with the broader business context
- A system of preventing the common causes of productivity problems
- A framework for mastering the essential talent optimization aptitudes
In this talk you'll learn how your team can level up and align its people strategy with the overall business strategy