lighttangent

Loading

Blog

What is Extreme Programming?

Extreme Programming popularly called XP is based on a set of engineering practices. XP focuses on technical aspects of software development. The 1st extreme programming project happened in 1996 before the Agile Manifesto was created.

The core of Extreme Programming

  • Customer Satisfaction – Empower developers to confidently respond to changing customer requirements, even late in the life cycle.
  • Teamwork – Managers, customers, and developers are all equal partners in a collaborative team. 
  • Self-organizing team – Focus on the problem and solve it as efficiently as possible as a team.
  • Communication – Extreme Programmers constantly communicate with their customers and fellow programmers.
  • Simplicity – Keep the design simple and clean
  • Feedback – Extreme Programmers get feedback by testing their software starting on day one. They deliver the system to the customers as early as possible and implement changes as suggested.
  • Respect and Courage – Every small success deepens their respect for the unique contributions of each team member. 

Extreme Programming Practices

  • Test Driven Development
  • Customer with the team
  • Pair Programming
  • Code Refactoring
  • Continuous Integration
  • Small Releases
  • Simple Design
  • Coding Standards
  • Collective Code Ownership

Summary

Extreme Programming (XP’s) primary focus is on the technical aspects of development and it puts great emphasis on software engineering practices. XP is all about programming, hence it is fair to say that XP is a set of practices and not a framework. Irrespective of the framework, a team can follow XP practices.

Source – Extreme Programming: A Gentle Introduction.

Scrum Master interview – Technical Questions

Here are technical questions you may encounter as part of the Scrum Master Interview. The intent is to understand your knowledge of Scrum, your experience as a Scrum Master, and your knowledge of Agile.

Refer to this article for a complete set of questions for a Scrum Master interview – https://www.lighttangent.com/how-to-prepare-for-a-scrum-master-interview/

Technical Questions (TQ) – Scrum Master Interview Questions

TQ1 – What is Scrum? https://www.lighttangent.com/what-is-scrum/

TQ2 -What is Agile Manifesto? https://www.lighttangent.com/agile-manifesto/

TQ3 -Was Agile created for Software Development? (Yes, agile methodology was primarily created for software development)

TQ4 – What is Kanban https://www.lighttangent.com/kanban-on-a-page/

TQ5 – What is SAFe? https://www.lighttangent.com/what-is-safe/

TQ6 – What is the Definition of Done (DoD)? https://www.lighttangent.com/definition-of-done/

TQ7 – What is Definition of Ready (DoR)? https://www.lighttangent.com/definition-of-ready/

TQ8What are the scaling agile frameworks? https://www.lighttangent.com/what-are-the-scaling-agile-frameworks/

TQ9 – Which framework is the best in agile?

TQ10 – What is the difference between Scrum and Kanban?

TQ12 – What is the difference between a Scrum Master and Agile Coach? https://www.lighttangent.com/scrum-master-vs-agile-coach/

How do I prepare for being a Scrum Master?

At a time in my career, I wanted to work as a Scrum Master, however, the biggest question for me was “ Where do I start to become a scrum master?”.  You may have a similar question and now when I reflect on this question, I feel it is normal to question yourself about how to prepare for a Scrum Master interview, and how to equip yourself with the knowledge to serve a scrum team. Based on my experience in transitioning to a Scrum Master role, here are seven pieces of guidance that you can follow –

Guidance 1 – How do I prepare for being a Scrum Master ?

Start with Why – Sounds familiar, the famous book from Simon Sinek. This is the most critical question to ask yourself, Why do I want to become a Scrum Master? Ask this question to yourself and convince yourself that you are clear on your path to being a Scrum Master.  If you have the conviction of becoming a Scrum Master, you are unstoppable.

Guidance 2 – How do I prepare for being a Scrum Master ?

Path to becoming a Scrum Master – Assuming you have zero knowledge of Scrum, creating a plan and following it will help you reach your goal of becoming a Scrum Master. This will lead to the 1st question that we discussed, Where do I start to become a scrum master?”. A few things that I followed to become a Scrum Master are as follows –

a) What is Agile?

b) What is the Agile Manifesto?

c) What are the various frameworks under agile?

d) What is Scrum?

e) Read the Scrum Guide

f) Read the Scrum Guide – Again and Again and Again and +++++++ (Scrum is easy to understand but difficult to master, reading the Scrum Guide once a month and reflecting on your experience and learnings on Scrum will make you understand Scrum better)

Guidance 3 – How do I prepare for being a Scrum Master ?

Scrum Master Certification – Understand various Scrum Master Certifications available, and go through the course outline before taking up a certification. The major advantage of doing a certification is to get the knowledge in a capsule format in a limited time.

Guidance 4 – How do I prepare for being a Scrum Master ?

Daily life of a Scrum Master – Understand what a Scrum Master does daily, day-to-day tasks, and challenges faced. Connect with Scrum Masters and ask them about the challenges they faced in their organization/teams.  Also, learn about their context, the processes followed, things working well, and things not working well.

Guidance 5 –How do I prepare for being a Scrum Master ?

Prepare for the Scrum Master interview – Here is a list of questions which you can go through for a Scrum Master interview.

Check this – https://www.lighttangent.com/how-to-prepare-for-a-scrum-master-interview/

Guidance 6 – How do I prepare for being a Scrum Master ?

Learn the tools used by Scrum Master – JIRA/Asana/Azure, these are some of the tools used by Scrum Masters with JIRA being the most commonly used. Tool knowledge will increase your confidence during the interview process. ( I asked a few Scrum Masters to give me a walkthrough of JIRA and that helped before I took up a Scrum Master job)

Guidance 7 – How do I prepare for being a Scrum Master ?

Apply Apply Apply – Now you are ready to take up a Scrum Master role, you know a Scrum Master, and you are aware of the challenges faced by a Scrum Master, it is time to apply for a Scrum Master role either in your organization/outside of your organization. Speak to your friends/colleagues/network and inform them that you are looking for a Scrum Master opportunity. My strong recommendation is to apply for internal job postings in your organization as many organizations promote career aspirations and do not necessarily look for prior experience as a Scrum Master. Keep trying and keep applying till you land up with a Scrum Master job.

14 Key Terms in Kanban – Everybody should know

Here are the terms that one comes across in Kanban. Understanding the concepts of these terms will help one in understanding Kanban.

Flow – Kanban is based on the theory of flow. Flow is of no use without value, in Kanban Flow is the movement of potential value through a system.

Kanban Practices – There are 3 practices in Kanban ( (1) Defining and visualizing a workflow (2) Actively managing items in a workflow (3) Improving a workflow

Kanban system – Kanban practices are collectively called a Kanban system

Kanban system members -Those who participate in the value delivery of a Kanban system are called Kanban system members.

Workflow – How work gets done + movement of potential value through a system.

Definition of Workflow (DoW) – This is the fundamental concept of Kanban. The explicit shared understanding of flow among Kanban system members within their context is called a Definition of Workflow (DoW).

Kanban Board – The visualization of the Definition of Workflow (DoW)is called a Kanban board.

Work Items – A definition of the individual units of value that are moving through the workflow.

Work in progress (WIP) – Any work items between a started point and a finished point are considered work in progress (WIP).

WIP limits – WIP stands for Work in Progress, part of actively managing items on a workflow practice. Controlling WIP helps in managing the workflow which means not adding new work items unless the in-progress work items are completed.

Service Level Expectation (SLE) – Forecast of how long it should take a work item to flow from start to finish. It serves 3 functions – right sizing, completion forecast, and how much age is too much age.

Throughput: The number of work items finished per unit of time. Note the measurement of throughput is the exact count of work items.

Work Item Age: The amount of elapsed time between when a work item started and the current time.

Cycle Time: The amount of elapsed time between when a work item started and when a work item finished.

Refer this page – Kanban on a page to know about Kanban in a nutshell.