Skip to main content

The 6 Powerful Questions of The Personal Agility System

The Personal Agility System is the simple framework I have been working on, to help people do more of what matters.

What really matters? That's a great question! Does the answer just roll off your tongue? For many people it doesn't. But if you don't know what matters, what difference does it make what you do? How can you be satisfied with your life and your impact on the people important to you?

At its heart, Personal Agility is a coaching framework to help you figure out and focus on the things that really matter to you. Personal Agility is based not on performing tasks but on asking yourself Powerful Questions.  A powerful question invites you to think and reflect. You know what is the right thing to do.

These core questions help you figure out and focus on what really matters. There are a total of six questions, five to ask yourself routinely and one to help you get unstuck:
  1. What really matters? -- This provides context for answering the other questions.
  2. What did I get done this week? -- Celebrate it and feel good about yourself (even if what you did was different that what you had planned last week)!
  3. What could I do this week? -- Keep you to-do’s in a place you will see them again.
  4. Of those things, which are important and which are urgent? - Triage against what really matters.
  5. Of the urgent and important things, what do I want to do this week? -- Take only as much as you think you actually get done. 
  6. Who can help? -- The question and the answer can both help you get unstuck. That person might be helpful too!


Comments

Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …