Importance of Zero Talent Virtues in Agile Software Development

This article explains importance of virtues that depict the attitude of a person than the talent. This is based on a very popular meme on social media which lists down zero talent virtues like being on time, doing extra, being prepared, etc and applies that into agile environment.

This article is an example of collaborative discussion between many contributors from PlayScrum Vadodara community. A special thanks to all the contributors: Anand Vyas, Anil Sharma, Bhavin Acharya, Chintan Sisodia, Deepak Joshi, Harit Pandya, Jay Pandya, Misha Vaidya, Rajesh Panchal, Sachin Patel, Satisha Venkataramaiah, Sneh Shahani, Vaibhav Dhingani, Vishal Shah

Please have a look at the article by visiting https://www.scrumalliance.org/community/articles/2016/june/the-importance-of-zero-talent-virtues-in-agile-sof

Case Studies, Problems and Solutions from Practitioners from 11 June 2016 - Practitioner's Corner

Problem 1: How do I select a pilot team for adopting and implementing Scrum ?

Solution:

• Select a project (pilot) which requires shorter delivery to market.
• Choose a mature Cross functional team, small in size which already has good knowledge on the application.
• Choose teams having better Engineering practices
• Teams which have little or no escalations
• Engage metrics team of the respective organization to do an Agile assessment for the chosen team.
• Most important, teams for which there is Buy-in from Senior Management.

Problem 2: Scrum Master is a developer. He is associated with a team which is working on Niche technologies. Problem the Scrum Master faces are below,

• Scrum Master and the team is overworked.
• At regular frequency, Team members frequently drop their papers.
• Though Management is able to provide an alternate (Backup \ Shadow) resource, it is pulling down team's velocity.
• There is lot of emphasis from Senior Management on Daily reports which Scrum Master finds it as a waste of time.

Solution :

After a long discussion it was understood that overworked team members were not the reason for team members quitting at regular intervals of time. It was understood that the niche technology was the driver behind team members logging in extra time and at the same time quitting. If the Management could take care of their needs, this leakage could be arrested.

As far as the reports go, the 'PlayScrum' practitioner's have suggested the 'Scrum Master' to keep adding metrics to the report, make it complex so that one day 'Senior Management' could come back saying that this report is no longer required.

Case Study : XP on top of Scrum increases mature Scrum team's Velocity

Top Management decided that entire organization has to transition from Waterfall to Scrum way of project delivery

Many projects across the organization's distributed teams started to use Scrum (in 2 week sprints) and velocity data was recorded for 1 year. After 1 year, when the Top Management wanted ways to improve velocity, by doing XP, the teams were able to show significant improvement in velocity - primary reason being in XP, team could pick up items as and when completed).

Thanks,
Natarajan

Open Problem Statement from 30th July 2016 - Practitioner's Corner - Chennai.

Problem Statement

This problem was brought to the table by a practitioner 'Scrum Master' in the 'Practitioner's corner'. It could not be discussed due to the lack of time. Problem statement below,

The Scrum Master's team is functionally and geographically distributed scrum team. Scrum Master and QA team is co-located in Chennai. Development team 1 sits at Singapore and Development team 2 sits in another geography other than the two mentioned above. 

Scrum Team does not connect regularly with Product Owner unless when it is the 'Sprint Review'. Zeroth sprint always runs ahead of the Scrum Team's sprint. In the Zeroth sprint, group of architects discuss with Product Owner and come up with 'Architectural stories' and 'Feature stories' which 'Scrum team' has to work on.Team follows a 2 month sprint window whose breakup is below,

• Build and QA happen in parallel in the the First month + Integration testing with Upstream and Downstream teams.
• QA team provides UAT support to business in the second month.
• Scrum Team does not have resources for working on Non functional requirements (ex. performance testing).
• Release happens at the end of every 3 months

Issue faced by the Scrum Team:

• We hear from the 'Scrum Master' of the impacted team (details below) that even though there is the above process followed, 

• The application in production has performance issues (especially - Non functional ones)

Due to lack of time, we were not able to take up this problem statement and figure out the root cause. 

This is an open problem statement which can be picked up for discussion in upcoming Practitioner's corner.

Thanks,

Natarajan

How to resolve team problems?

This scenario was discussed in Practitioners Corner held at Pune. Below are the notes of the discussion.

How SM can help PO if PO is unclear?

This scenario was discussed in Practitioners Corner held at Pune. Below are the notes of the discussion.

The scenario of the organizational structure for the project is described in below figure.

Situation is like Product A and Product B. Product B is a replica of Product A. PO accepts but super PO rejects.

Typical reasons for rejecting

PO’s boss is aware of internals and has different level of understanding.

PO, Super PO, SM are at client side.

No acceptance criteria, process of agreement

Solutions

Get a Legacy System Expert

Get aligned on acceptance criteria.

Gap analysis

Sprint sign off process

Definition of ready to be sent.

What is PlayScrum?

PlayScrum is a community of agile practitioners passionate about playing the Product Development game using Scrum. Objective of the initiative is to “To help people learn and play Scrum effectively.”

The members of the PlayScrum community are known as Players.

Players across India meet once a month in their respective cities to update themselves on latest happening in Scrum. Currently there are seven PlayScrum meetup groups all over India: Pune, Chennai, Bangalore, Delhi, Hyderabad, Kolkata and Vadodara with more than 2200 Players (as on May 2016). PlayScrum user groups in Pune, Chennai, Delhi, Bangalore and Vadodara are recognized by ScrumAlliance.
The community has organized around 50 regular meetups, 10 half-day metups and 5 full-day meetups across India and discussed a wide range various topics including:

• Techniques like Impact mapping, Experience mapping.
• Concepts like Ways to Scale Scrum, Coaching models, Big Team Dynamics, Agile methodology which is suitable for an organization (What is good for me?)
• Applications like Organizational transformation, Organizational Change,  Fix bid projects using Scrum , HR and Performance challenges, and many case studies that people bring in. 

Apart from regular meetups the community has also organized around 10 half-day meetups, 5 full-day meetups.

PlayScrum community also organizes Practitioner's corner. Practitioner’s corner is a platform which provides

- to provide solutions to problems being faced by people to the people who practice Scrum

- to provide opportunity to experienced practitioners to solve novel problem and

- for novice it is an opportunity to learn how experienced people work.

Twitter: @PlayScrum

Facebook: www.fb.com/PlayScrum

Email:   meetup@playscrum.com

Website: www.playscrum.com

Social Scrum

“Social Scrum is PlayScrum community's pioneering initiative to combine agile practices into solving problems of the society”

Facebook: www.fb.com/SocialScrum/