The Agile Daily Standup - AgileDad AgileDad ~ V. Lee Henson

The Untold Story Behind The Key Bridge Collapse in Baltimore

How to connect with AgileDad:

- [website] https://www.agiledad.com/

- [instagram] https://www.instagram.com/agile_coach/

- [facebook] https://www.facebook.com/RealAgileDad/

- [Linkedin] https://www.linkedin.com/in/leehenson/

T-Shaped Personas

Key Concepts


A persona is an abstract representation of a typical user or customer. We often focus on the buyer persona and the moments-that-matter for our buyer’s journey. This article focuses on the customer already using our product or service.
A feature is an important part, quality or ability of a product that makes it distinct or better; it usually contributes to the overall value proposition.
A product feature matrix maps product(s) on one axis, to features on an intersecting axis. It is typically used to compare competing, similar products, or differentiate a product’s versions from product Gamma to Gamma+, Gamma 2.0 and so on.
The T-Shaped person is a talent management concept, attributed to McKinsey & Company, that describes the depth or domain expertise of an individual along the vertical stroke of the letter ‘T’, while also describing that same individual’s breadth across varied other disciplines along the ‘T’ horizontal bar.
A T-Shaped Persona is a new concept. It’s a business strategy tool, similar to the talent concept above, visualized by a ‘T’; it also conveys a breadth and depth. Its differences start with its job — act as a visual guide to inspect a persona’s adoption and use of our product(s). The vertical stroke of the letter ‘T’ signifies depth of product experience, while the ‘T’ horizontal conveys typical persona attributes like geographic, firmographic, occupational, and other traits.



How to connect with AgileDad:

- [website] https://www.agiledad.com/

- [instagram] https://www.instagram.com/agile_coach/

- [facebook] https://www.facebook.com/RealAgileDad/

- [Linkedin] https://www.linkedin.com/in/leehenson/

Stop Doing So Many Spikes - Mike Cohn

One of the more common mistakes I see teams make is relying too much on spikes. A spike is an activity a team performs to get smarter about something. With a spike, a team isn’t trying to immediately deliver a new capability; instead, they are building the knowledge that will allow them to deliver the new capability later.Spikes are a great tool, and I’d expect every team to use them...but not on everything they work on.The best use of a spike is to reduce excess uncertainty. This could be uncertainty about how a feature should work or about how it will be built.A team may opt, for example, to spike the user interface for a particular feature. Or it may use a spike to determine if a technical approach is feasible or will perform at the required level.Each of these can be a good use of a spike. The problem comes when a team wants to use a spike on everything. Spikes should be used only in cases of extreme or excessive amounts of uncertainty. Spikes should not be used to reduce the typical, garden-variety uncertainty that exists in all work.Further, spikes should not be used to eliminate uncertainty. Teams need to be comfortable bringing work into their sprints or iterations with open issues remaining.Is your team reluctant to allow work into a sprint with any remaining uncertainty? That’s sometimes the result of team members feeling excessive pressure to estimate perfectly, to always achieve the sprint goal, or to always deliver everything that they brought into a sprint.If that is happening, a Scrum Master or coach needs to work with outside stakeholders or whomever is creating these unrealistic expectations. Sometimes it’s even the team members putting this pressure on themselves.But what’s the problem with frequent spikes anyway? It’s that overuse of spikes extends your time to value. This is especially true when the spike is done in one iteration and the rest of the work in a subsequent iteration.Overuse of spikes also reduces the extent to which teams overlap work. This can increase the burden on testers.For example, consider the case of a programmer who uses a spike to reduce the uncertainty of a backlog item. If that item is brought into the next sprint, the programmer’s work has been made simpler by the spike, but the tester’s has not.If your testers are struggling to keep current with the programmers, consider whether the team is doing too many spikes. It’s a good question to ask yourself even when the testers don’t seem overburdened, if you want to succeed with agile.

How to connect with AgileDad:

- [website] https://www.agiledad.com/

- [instagram] https://www.instagram.com/agile_coach/

- [facebook] https://www.facebook.com/RealAgileDad/

- [Linkedin] https://www.linkedin.com/in/leehenson/

6 Micro-Habits of Highly Effective Leaders


Great managers follow simple habits and practices to stay highly effective.
They reframe fear as a sign to evaluate multiple options, ask questions, or reconsider assumptions instead of letting fear get in the way of making decisions or taking action.
Instead of giving power to naysayers by allowing them to influence their thinking or how they make decisions, highly effective managers stay away from them.
By working on things within their control instead of wasting time on things outside their control, highly effective managers expand their circle of influence.
Maximizing their team’s potential is their primary focus. By highlighting each individual’s strengths and combining them with the right opportunities, highly effective managers build high-performance teams.
Effective managers are highly self-aware of the limitations of their minds. They don’t let cognitive biases get in the way of how they think or make decisions.
They use their peak productivity period to do some of their best work. Matching energy to the cognitive demand of their work makes them highly effective.

How to connect with AgileDad:

- [website] https://www.agiledad.com/

- [instagram] https://www.instagram.com/agile_coach/

- [facebook] https://www.facebook.com/RealAgileDad/

- [Linkedin] https://www.linkedin.com/in/leehenson/

The BEST way to Improve Company Culture Is To KILL It First...

You’re working long hours, for low pay, either in an open office environment that nobody likes or working remotely and feeling like you’re going to wake up tomorrow to one of those dreaded HR meeting invites.

There doesn’t seem to be any kind of work-life balance anymore, because the gap between the two has disintegrated, and life is so expensive right now that you’re perpetually working in larger chunks to salvage smaller slivers of life.

You’re not happy. I get that. And if we’re here to be honest, I’ll tell you I’m not happy either. All respect, but I’m not here to listen to a bunch of complaining or to resolve interpersonal issues all day. I’m in the same boat as you, only I don’t have anyone to complain to.

How to connect with AgileDad:

- [website] https://www.agiledad.com/

- [instagram] https://www.instagram.com/agile_coach/

- [facebook] https://www.facebook.com/RealAgileDad/

- [Linkedin] https://www.linkedin.com/in/leehenson/

The Art of Getting a Good Nights Sleep

Is it really possible to get a good nights sleep? Join V. Lee Henson as he reveals tips and tricks to help you get the rest that you need.

How to connect with AgileDad:

- [website] https://www.agiledad.com/

- [instagram] https://www.instagram.com/agile_coach/

- [facebook] https://www.facebook.com/RealAgileDad/

- [Linkedin] https://www.linkedin.com/in/leehenson/