International Institute for Learning
APRIL 19, 2023
DA was developed in 2011 by Scott Ambler and Mark Lines and is based on Scott’s work at Rational Software and IBM. Dean Leffingwell released the first version of SAFe in 2012. DA defines “process blades” to describe common enterprise capabilities. Interestingly, Dean also worked at Rational.
Scrum.org
APRIL 7, 2022
Pryzbilla and his colleagues (2020) analyzed fluid teaming in IT environments and found that it is often used to bring highly specialized skills together to solve difficult problems. Edmondson (2012) argues that dynamic teaming is important to share and encourage learning. What defines fluid and stable teams?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Planio
AUGUST 1, 2023
6 rules to follow How to bring strategy and tactics together: 5 examples for different teams 1. Product development teams 2. Digital marketing teams 3. Sales teams 4. Customer service teams 5. This fictional bank defined a high-level strategy to increase customer trust. Map out KPIs and milestones.
Scrum.org
FEBRUARY 15, 2020
In the movie Avengers (2012), The Mind Stone allows the user to control the minds of others and can control what they do. Similarly Scrum in product development, through the process of empiricism can control what can be "Done" or delivered within a time frame to the end-users; to satisfy their needs.
Herding Cats
APRIL 16, 2019
The following material comes from conferences, workshop, materials developed for clients. The overarching theme is focused on defining what Done looks like, assessing progress toward Done in units of measure meaningful to the decision makers. Mathematical and Science Writings (#MathSci). Presentations and Briefings.
Teamweek
JUNE 25, 2020
Asana was founded in 2008 by ex-Google and ex-Facebook engineers with the aim to make team collaboration better. Incredibly, it took almost four years to launch it commercially in 2012. That’s because these teams find Asana too complex to use, unintuitive, and expensive. Particularly, for small teams. Too Complex.
Herding Cats
JUNE 12, 2018
The very technical answer to this question is the sample rate can be determined by a Nyquist sample rate analysis of the underlying non-stationary stochastic process of any typical software development project. This approach gets you a D in the statistical assessment class. Standish Report and Naive Statistics. Standish Number.
Expert insights. Personalized for you.
59 
Let's personalize your content