Agile Scrum Flashcards
5 Scrum Values
- Commitment
- Courage
- Focus
- Openness
- Respect
3 Roles in Scrum
- Product Owner
- Scrum Master
- Development Team
Number of people in a Scrum team
3-9 dev members, not including PO and SM
User Stories format
As a (type of user), I want to (perform some action) so that I (can achieve some goal/result/value).”
Purpose of a user story
The purpose of user stories is to explain the roles of users in a system, their desired activities, and what they intend to accomplish by successfully completing a user story. For Agile teams, user stories are the primary method of identifying user needs.
What are acceptance criteria?
Acceptance criteria are a formalized list of requirements that ensure that all user stories are completed and all scenarios are taken into account.
Put simply, acceptance criteria specify conditions under which a user story is fulfilled.
Concisely written criteria help development teams avoid ambiguity about a client’s demands and prevent miscommunication.
What are acceptance criteria used for?
- To define boundaries - Acceptance criteria help development teams define the boundaries of a user story. In other words, acceptance criteria help you confirm when the application functions as desired, meaning that a user story is completed.
- To reach consensus. Having acceptance criteria synchronizes the development team with the client. The team knows exactly what conditions should be met, just as the client knows what to expect from the app.
- To serve as a basis for tests. Last but not least, acceptance criteria are a cornerstone of positive and negative testing aimed at checking if a system works as expected.
- To allow for accurate planning and estimation. Acceptance criteria scenarios allow for the correct division of user stories into tasks so user stories are correctly estimated and planned.
Types of AC writing
- rules-based (checklist)
2. scenario-based - BDD
Adv of using BDD templates for writing AC
helps with getting across requirements, envisaging various use cases, and further using scenarios for manual and automated acceptance tests.
used for writing acceptance tests that ensure that all the specification requirements are me
Example of BDD template
As a logged-out user
I want to be able to sign in to a website
So that I can find access my personal profile
Scenario: System user signs in with valid credentials
“Given I’m a logged-out system user
and I’m on the Sign-In page
When I fill in the “Username” and “Password” fields with my authentication credentials
and I click the Sign-In button
Then the system signs me in”
Why would you like to re-join Fidelity?
- Fidelity set a very high bar
- Know that I will be surrounded by consummate professionals
Weaknesses
Fretting - feeling like you are responsible for team
Strengths
Communication
Fairness
Attention to detail
Following up
Greedy Learner
Role of Systems Analyst
- Ensuring that the business needs are well understood
- Elicit requirements for development of user stories
- Work with PO and SMEs
- Work with Tech Leads and development team
Fidelity Capital Markets
Fidelity Capital Markets is the institutional trading arm of Fidelity Investments®, providing trading products & services to a wide array of clients, including buy-side institutions and hedge funds, as well as to Fidelity®’s own businesses.
$1,382 BILLION TOTAL Assets under management
Fixed Income
Fixed Income has invested in state-of-the-art trading floors in Merrimack, NH,
Boston, and London, which are critical for navigating the increasingly complex
global fixed income markets and essential for a seamless, comprehensive view of
global investment opportunities
What is Fixed Income?
Fixed income is an investment approach focused on preservation of capital and income. It typically includes investments like government and corporate bonds, CDs and money market funds. Fixed income can offer a steady stream of income with less risk than stocks.
How to manage difficult stakeholders?
- Transparency, communciation, bring them on the journey with you
- AML model, data science jargon
Presentation skills
Tech talk on ‘Intro to Machine Learning’, later asked by GM to present to EMEA-wide audience
LIME presentation
Brown-bags in Anaplan to SF and London
Sprint planning
- Create a plan for the sprint
- Everyone commits to sprint goals
- Assign tasks
Sprint refinement
- Refining or grooming stories
- Adding detail, estimates and order of items in Product Backlog
- Items should be clear enough and small enough
Definition of Done
Purpose to drive quality, consistency and transparency
- Release Notes Prepared
- AC met and approved
- Developement/ETL complete
- Unit tests prepared and passing
- Static code analysis successful
- Peer review including final changes complete
- Build deployment to dev
- Integration Environment complete
- Functional tests developed and passing
- Non-functional tests developed and passing
- Build and deployment to staging complete
- Create necessary documentation
How would you go about eliciting requirements?
- Workshop
Name a time you succeeded
- Rule Evaluation Framework
- Saving $200,000 per evaluation of ruleset per client
- Java blog on microbenchmarking
Name a time you failed
- First fraud detection model
Agile Advocates
The overarching objective is to ensure the effective application of the Agile Scrum process framework in Nenagh.
- Boyband of representatives from different functions
- Defining and documenting the R&D Scrum framework
- Training
- KPIs
- Information radiator dashboards
- Governance
Data Science
Continuous improvement - how to implement
Retrospectives - opportunity for the Scrum Team to inspect itself and create a plan for improvements
One productivity improvement task identified as part of the previous Scrum retrospectives will be included in the following sprint.
Role of PO
- Time spent should be 80:20 (future focused: current sprint)
Example of leadership
- Scrum Master dual role
- Coder Dojo
- Mentor to junior data scientist
- Being mentored and seeking mentorship from inspiring professionals
- Anaplan recruitment drives, leading interviews
- Overhauling junior software engineer interview
Outside work:
- Big Brother Big Sister programme mentor
Questions for Fidelity
- Makeup of the team, mature/newly formed
- Do we have clear Product Owner, well-defined stakeholders
- Can you tell me a little about the product?
- How is remote working going for you all?
Challenge you overcame
Adopting a framework in Data Science
- Coding Standards
- Toolsets
- Project structure
- Source version control
- Code review
Challenge you overcame
Adopting a framework in Data Science
- Coding Standards
- Toolsets
- Project structure
- Source version control
- Code review
Dealing with ego in high-calibre teams
- Using empathy to understand both perspectives
- Talking to each member individually
Challenge you overcame
- Adopting a framework in Data Science
- Coding Standards
- Toolsets
- Project structure
- Source version control
- Code review
- Dealing with ego in high-calibre teams
- Using empathy to understand both perspectives
- Talking to each member individually
- Relaying under-performing model results to stakeholders
Scrum Advocates KPIs
- Customer satisfaction
- Team velocity
- Sprint burn-down
- Cumulative flow
- Team health check
- Software Quality
- Sprint Goal Met
- % User Stories Committed to VS % User Stories Completed
- Sprint Ceremony Time Vs. Total Time
Scrum Advocates KPIs
- Customer satisfaction
- Team velocity
- Sprint burn-down
- Cumulative flow
- Team health check
- Software Quality
- Sprint Goal Met
- % User Stories Committed to VS % User Stories Completed
- Sprint Ceremony Time Vs. Total Time
Aims to capture info on:
- Product
- Efficiency
- Team
- Schedule
Velocity
Team’s ability to turn ideas into functionality
or
The amount of value delivered in each sprint
Burndown
Tracks the total work remaining in the sprint and projects the likelihood of achieving the sprint goal, by tracking the remaining work throughout the iteration
Cumulative Flow Diagram
Shows the various statuses of work items for an application/version/sprint.
CFD useful for identifying bottlenecks
Scrum Ceremony Time
Captured using user stories
- how much time is being spent in ceremonies
- who is working on each ceremony
- where can we derive efficiencies from
- impact on the sprint if we go below a certain time limit for these ceremonies
Team Health Check
11 indicators
- easy to release
- suitable process
- codebase health
- value
- speed
- mission
- fun
- learning
- support
- teamwork
- pawns or players
Team Health Check
11 indicators
- easy to release
- suitable process
- codebase health
- value
- speed
- mission
- fun
- learning
- support
- teamwork
- pawns or players
Promotes self-awareness within team, and offers view of systemic problems
Customer Satisfaction Score
How satisfied are you with the latest sprint?
NPS
How likely are you to recommend the work of the Scrum Team based on the delivery of work in the latest sprint?
0-6 Detractors
7-8 Passive
9-10 Promoters
Scrum Governance
Quarterly checkpoint/Audit
