Photography may sound simple but is actually a problem of complex domain. There are many variables — light, subject, motion, distance, composition, framing — that come into play while capturing an image. With the current range of cameras equipped with highly adaptable sensors (empiricism), many of these variables can be ignored to an extent and great images can be captured with the press of a button.

I am passionate about Scrum as well as photography and when I thought of writing my first blog, I thought of sharing important lessons that I found useful while supporting Scrum and taking photographs.

Lesson 1: The Three Leg Rule

For creating awesome images, a photographer has to understand 3 important aspects which are key to capturing images: shutter speed, aperture, and ISO rating. Not paying attention to any one of these impacts the quality of the image captured.

For Scrum to create maximum business impact, empiricism must be upheld by 3 pillars of Transparency, Inspection, and Adaptation. Every Scrum team should be paying attention to all three aspects. Ignoring any one of them is going to impact Scrum implementation adversely.

Lesson 2: Perspective and Viewpoint

A simple photograph can have a dramatic effect if the perspective and viewpoint is changed while shooting the image. A shift in perspective or viewpoint brings out so many different details in the object that otherwise would not be visible.

Scrum thrives on self-organizing, cross-functional teams. The perspectives and opinions that are brought by individuals to the team are valuable. Whether it is planning poker for estimating the work or a Sprint Retrospective to look at the Sprint gone by, paying attention to everyone's perspective and taking them into account takes the Scrum team on its journey of high performance. Overshadowing the teams' thoughts with the Hippo's opinion has a devastating impact on other team members.

Lesson 3: Light and Management

Light is an important factor while capturing images. But it is out of the control of the photographer. In any given situation, we need to capture images with the amount of light that we have; we cannot ask for more or less. We need to tweak our settings to make the best use of the available lighting conditions and create great images.

Management, in any organization adopting Scrum, is like the light for the photographer. One cannot ask for more or less. We need to work with what we have and make the best use of it to "promote and support Scrum, within the organization as defined in the Scrum Guide." The best way to deal with management that I have experienced is to make them feel important and take their help in tackling organizational impediments.

Lesson 4: Borrow All that Which Is Good and Helps You Be Better at What You Do.

A good camera is just the starting point. For capturing great images, in a variety of situations, we might need much more than just a good camera. First and foremost, we need the skills of an able photographer to identify the right frame and composition. Then we might need a wide-angle/zoom lens, a flash gun, a tripod or may be a remote release. Using all the gear that we can make use of; we can create stunning imagery. This all would help only if we don't let go of the 3 legs of photography — Shutter Speed, Aperture and ISO rating.

Scrum does not create software by itself. It is a framework that provides certain ground rules which can help any team/organization to better its existing software development process. Within the Scrum framework, Scrum Teams may utilize practices, methods from different frameworks, or processes that they find useful. Some common practices that I have seen teams use and benefit from are test driven development, pair programming, user stories, and story points. All these practices stand as long as the key pillars of Transparency, Inspection and Adaptation are not compromised.

Lesson 5: Finally, the Results Can Be Verified Only In Hindsight.

A moment is captured the instant the shutter is released. No matter how much planning goes into capturing a moment, one can only say the image is good, bad or ugly after looking at the image once it is caputred. That's when one learns what all aspects can be improved, to capture a better picture.

With Scrum, unless the Sprint is ended and an increment is created, we do not know whether it adds value to the product or not. We may do necessary planning, but given the complex nature of our problems, will we get the desired results at end of every sprint, every time; maybe not. Although, we can always look at the results and retrospect over the sprint about how to do better in upcoming sprints.

Would love to hear your thoughts and learn; what were your experiences while supporting Scrum in your journey?