Beruflich Dokumente
Kultur Dokumente
servant leadership is a participative leadership, facilitative and involded hands on with daily activities of the t
epic = capability
removal of work
Fibonacci series for relative scoring - plannign which stories can be worked on in the upcoming sprint
Definition of done is provided by "The Team"
high performance teams trust each other - transparency is key
Risk adjusted backlog will have value driven features and costly risks
story board is when team is documents to understand the need and flow of the product
wire frame a raw sketch of how a screen looks like
schedule is by estimating story points and applying velocity
a spike is an experiment performed to provide a basis for making a design or developemnt decision or to answer the
questions posed by an uncertainity or risk
kaizen - small changes
kanban - signal
ATDD is the technique based on the test driven approach where the team discusses the acceptance criteria with the Busine
a detailed set of tests are designed in advance and is accepted by the business and stakeholders. The ATDD cycle starts fr
discussions and then team distill this, followed by development and demo of item as mentioned in acceptance before mark
as DONE
A project manager in an XP team ensures that the team works well with the rest of the organization. A PM is more focused
managing external stakeholders.
Sync continuous integrationPair integrates their code after each pair-programming episode in no more than a couple of hou
waits for the build to complete and the entire test suite to run before proceeding is an example of synchronous continuous
integration
asynchronous continuous integration -
Contain risk - since team is keeping some contingency reserve to take care of unexpected tasks it falls in Contain. In conta
plan contingency reserve to take care of risk
This is a mitigate strategy as by taking this step team is trying to lessen the probability of risk.
This is not avoid-since team is not trying to steer clear of the risk. If team has decided not to release the product as a risk
that could have been categorized as avoid
This is not contain- because team is working on mitigation plan rather than having contingency plan , if team decided to
developers on standby for next 3 months to take care of any escape defect, that would have been the contain strat
This not evade- since this implies that team does nothing about it and expecting to be lucky which not the case here is.
Business value delivered chart. The entire enterprise (business, management, and development teams) needs the line o
velocity (points/time) dashboard-type view of work management which in other terms is a business value delivered c
Release duration is 3-12 months for new develoment lon term projects
Ground rules - Team is responsible for creating and enforcing the ground rules, scrum master should ensure that team doe
Agile manifesto - agile alliance in 2001
Multistage integrstion builds involve the running of additional tests for performance, load, and stability. These are slow to r
in most cases run asynchronously as part of a slower secondary build
Parking lot chart
This contains a large rectangular box for each theme in a release annotated with the name of the release, number of sto
their total estimate and a swim lane to indicate completion of the theme. It is great for compressing a great deal of inform
a small space.
Risk Census
Risk census is the terminology used to describe a list of risks that are faced by a project and are not common to all projec
risks are specific and unique to that particular project
At the end of second iteration, actual cost = 22,500 and story points completed = 60.
burn down - amount of work on a vertical(y axis) and timeline (x axis) on a horizon
As time progresses we keep track how much work is still not done
burnup - we track how much work weve completed, so the curve is going up, not d
scope change is tracked along with the progress so burnup is better