1. Scrum Master – Rolesand Responsibilitiesasa ‘Servant Leader’
Functional/Behavioural Role
 I be Agile first now before implementing Agile. My view of work to build self-managing and self-
organizing teams and build trust between team members. And scrum framework gives me the best
platform to explore be disciplined with time-boxing and make the teams high performing under time-
driven activities.
 I see Agile is more about the improved soft-skilled communication platform as we work in agile with
closer customer collaboration, individuals & interactions and I would transmit to my team for ‘Agile
Practices’.
 I will make sure my team work as a cross-functional team where each team members are capable to
crossing their boundaries.
 Agile Manifesto asked me to be experienced with the frequent and early delivery with working software
as the measure of progress.
 I learnt from agile to fail early, learn early from failure and then showing the success at early level.
 Agile taught me to be adaptive and respond to change and that leads me to change my mindset as
agility.
 As a scrum master, would educate my team with typical sprint cycle process which covers scrum roles,
artifacts and ceremonies.
 As a scrum master, I would facilitate and set up ceremonies (Sprint Planning, Daily Stand Up, Sprint
Review and Sprint Retrospective)
 I do help the team maintain their sprint burndown chart
 I shield the team from interruptions during the sprint
 Scrum Master Role taught me to coach and educates team with the scrum disciplines, framework and
rules to be followed and moreover how to remove impediments and to facilitate team's decisions.
 I walk the product owner through and would make sure that there sufficient stories are present in
backlog for the upcoming sprint.
 I do encouraging collaboration between the Scrum team and product owner.
 Daily Scrum Meeting showed me how to plan in daily basis with 3 key Questions (What have I done
since last daily scrum, What will I do till next daily scrum and what is my impediments if any) and
educate team members to finish daily scrum meeting in 15 minutes.
 Sprint Retrospective taught me to learn from mistakes, asks for improvement by each team members
and mention positive outcomes.
 Sprint Review is an art - Agile showed me to demonstrate how to achieve success with DoD and
moreover, if any items not completed , then to show as "Coming Soon" display in canvas for the
particular item to make customer hopeful and with expectation for the next iteration.
 In Sprint Planning meeting, as a Scrum Master, I made my team is sync with PO and make PO is
available mostly in planning meeting to a) make mutual agreement with the team for defining "Sprint
Goal" and b) to clarify questions with PO for estimating the task closer to appropriation.
 I taught my team how to follow “Definition Of Done (DoD)” in Task Level and PBI Level.

2. o Task Level DoD
 Unit Tested
 Peer Reviewed
 Checked into source control
 Checked-in code doesn’t break the build
 Task board has been updated and remaining time for each task = 0.
o Product Backlog Item (PBI) DoD
 All acceptance criteria have been met
 Automated accepted tests confirm that the new feature works as expected.
 All regression tests verify successful integration with other functions.
 Any relevant build/deploy scripts have been modified and tested
 Working functionality has been reviewed and accepted by PO.
 End-user documentation has been written and reviewed (if required)
 Advanced Scrum Master Techniques taught me how to measure Fixed-Date Project and Fixed-Scope
Project and also derive with the estimated velocity range to provide the visibility to the customer that
how much minimum features to be delivered as MVP (Minimum Viable Product) or MMF (Minimal
Marketable Feature) at least by achieving lower limit of velocity.
 When I worked as a Scrum Master with globally distributed team, I always would make sure all the
team members can fall in common time zone with suitable timings for everyone's comfort and
infrastructure/process is already in place to avoid delay in timebox events/ceremonies.
 I do always attend “Scrum of Scrums” meeting weekly twice/thrice when project is distributed between
multiple scrum teams and obvious interdependency between all the teams.

3. Technical Roles as a Scrum Master
As a technical role of Scrum Master, would make sure that team has specific practices as
below for successful delivery in Agile methodology.
Test-Driven Development:
 The stepping stone of Agile Lean development – This approach reduces cycle time,
eliminates overproduction and wastage in shorter iteration.
5. Refactoring
Code
4. Run all the tests
and see all the all
tests pass with new
feature
3.Write Code for
new feature
2. Run all the
tests and see the
if new test fails
1. Add a test for
new feature
Acceptance Test Driven Development (ATDD)
Acceptance tests arefrom the user’s point of view – the external view of the system. They examine
externally visible effects, such as specifying the correct output of a system given a particular input.

4. Extreme Programming
The specific engineering process when requirement changes so frequent – may be
tomorrow ; so programming can be done for today on assumption that changes will happen
anytime.
4. Pair
Programming
3.Simple Design
2. Refactoring
1. Test Driven
Development
Continuous Integration
 Keep code ready to ship
 The goal is to be able to deploy at any time
 Integrate your code every few hours
 Keep your build, test and other release infrastructure up to date
 Each Integration should be as close to real release