The world’s most popular and easiest to use icon set just got an upgrade. View cheat sheet.xlsx from BA 325 at Lander University. X P(X = x) 2 0.3 3 0.2 4 0.1 5 0.1 6 0.3 Find the expected value E(X)E( X). Black jack for fun. Round your answer to one decimal place.
This document is a quick cheat sheet showing how the PEP 484 typeannotation notation represents various common types in Python 3.
# Python 2 only import anydbm import whichdb import dbm import dumbdbm import gdbm # Python 2 and 3: alternative 1 from future import standardlibrary standardlibrary. Installaliases import dbm import dbm.ndbm import dbm.dumb import dbm.gnu # Python 2 and 3: alternative 2 from future.moves import dbm from future.moves.dbm import dumb from.
Technically many of the type annotations shown below are redundant,because mypy can derive them from the type of the expression. Somany of the examples have a dual purpose: show how to write theannotation, and show the inferred types.
Variables¶
Python 3.6 introduced a syntax for annotating variables in PEP 526and we use it in most examples.
Built-in types¶
Functions¶
Python 3 supports an annotation syntax for function declarations.
When you’re puzzled or when things are complicated¶
Standard “duck types”¶
In typical Python code, many functions that can take a list or a dictas an argument only need their argument to be somehow “list-like” or“dict-like”. A specific meaning of “list-like” or “dict-like” (orsomething-else-like) is called a “duck type”, and several duck typesthat are common in idiomatic Python are standardized.
You can even make your own duck types using Protocols and structural subtyping.
Classes¶
Coroutines and asyncio¶
See Typing async/await for the full detail on typing coroutines and asynchronous code.
Miscellaneous¶
Decorators¶
Decorator functions can be expressed via generics. SeeDeclaring decorators for more details.
Team Estimation Game
Start with a stack of ranked story cards. The team will arrange the cards so the smallest size items are on the left and the largest items on the right. Items with the same or similar size should grouped together in vertical columns (the same place in the left-right direction).
Place the first (highest ranked) story card in the middle of the table (or in the middle of the board or wall)
Team members take turns estimating in a round-robin manner. On each turn, the player has two options, as shown below. With both options, the player will explain to the team the reasons for his or her estimate.
Take the top story card off the stack and place it on the table based on its estimated size
Move a previously placed card to a new location if you think it should be estimated differently
During a player’s turn, other team members may speak only to ask clarifying questions; they must not express their own opinions during another player’s turn.
After the last story card has been estimated, each player may take one more turn to move a card if he/she wants to.
Assign story point values to each group of cards. Even numbered teams use the pseudo-fibonacci sequence (1,2,3,5,8,13,20,40,100), and odd numbered team use powers of 2 (1,2,4,8,16,32,64,128)
You may not have stories for every number in this sequence.
Numbers represent the relative size/effort estimated for each story. For example, 3 story points is approximately 50% more effort than 2 story points, and 8 points is two times the effort of 4 points.
8 5 jacks or better. The Team Estimation Game was originally developed by Steve Bockman
Using color to visualize your backlog
What aspects of your stories are important for estimation? Discuss this with your team
Example: type of materials used, number of pieces, method of construction, etc.
This cheat sheet was part of the agile42 speech together with Propero Solutions on the Scrum Gathering Shanghai 2010
Cheatsheet 1 3 2 0 4
Latest Posts
April 17, 2020
Manage flow, not people!
April 15, 2020
Double Down on Scrum Fundamentals: Help Remote Teams Thrive
1/3 Divided By 2
Teams have moved to remote work: the great news for Scrum teams is that you already have the building blocks in place allowing you to succeed
April 10, 2020
How to work remotely as a team – Part 2
April 9, 2020
Complexity, Chaos, and COVID-19
Cheatsheet 1 3 2 0 0 Driver Download
Applying Cynefin & Complexity Thinking to navigate the COVID-19 crisis: a panel webinar recorded on April 2, 2020
April 9, 2020
Cheatsheet 1 3 2 0 9h 1 3h 4
Like a breath of fresh air.
Boost your Easter weekend with Carrington-Brown's Rap for agile42