Ruling emotions


Alain de Botton on Emotional Education @The School of Life
Source: https://youtu.be/W9X7u-MeJz0

“Whenever you are talking about your project, you seem to be sad,” my friend’s words struck me like lightening. Sadness was clearly not the emotion I wanted to stir up with relation to the initiative I felt responsible for. Sadness brings us dangerously close to doubt. Ideally, change should be linked with hope rather than fear, and doubt. Granted, some longer projects seem to run forever and project participants might become anxious – concerned about the end result, tired of the pressure of time, the constant stream of challenges. But this is something we, as project managers, should find ways to counter. Even when circumstances are tough. After all, we are supposed to manage the change. Of course, a sense of urgency by itself isn’t necessarily a bad thing. But we should deal with any negative emotions arising from or exacerbated by that change. Best – before they even appear. The worst thing we can do is allow them to rule us.

Personally, I link maturity with the ability to manage one’s emotions. Consider this for a moment – what’s typical in a child’s behavior? Emotions control the child rather than the other way round. Tantrums are one noticeable example. By contrast, a responsible leader seems to roam the sea of organizational challenges steadily, seemingly emotion-less, wielding emotions like a weapon or tool, drawing upon them only when required. The leader’s stability, predictability with respect to her emotions provides a solid ground for all the leaps the team has to make. Instability fosters doubt and mistrust. A positive outlook will be shared, so will a negative one.

See also
I Made A Mistakehttps://progressblog.com/2012/04/07/i-made-a-mistake/
The Stage is for the Childhttps://progressblog.com/2008/08/07/the-stage-is-for-the-child/

Why vs. What

Road leading into fog

Whenever a client wants us to start a new venture with them, to initiate a project together, we work on defining business requirements (apart from making sure there is a business case in the first place). Traditionally, Business requirements form the “what” of the project. They provide an explanation on what should be built to achieve the expected return on investment. It is uncommon to find a detailed, technical description there. From a technical perspective, finding a flowchart or field definitions in a BRD (Business Requirements Document) is rare. As the document is owned by the client and often prepared by her, as professionals on the supplier’s side, we often expect from our customers not to cross the thin line between the “what” and the “how”. Figuring out the “how” is the supplier’s job. It’s the space where he can analyze the work at hand, translate the more general, business perspective into functions, data structures and flows, paired with interfaces required to interact with the future solution. Among others. This is how functional requirements are born. They form a pair – business “reqs” and functional “reqs,” they should directly relate to one another, where business requirements are the “what” and the functional requirements – the “how.” In a way, the BRD is part of a mandate to start a project, whereas the FRD (Functional Requirements Document) – a contract describing how the project result is to be built.

Here’s the challenge. Agile is founded on the premise that suppliers and customers are able to work out requirements collaboratively in the form of user stories, maintained in a backlog of remaining work, detailed iteratively as needed – based on priority / proximity, aligning in tight iterations and frequent feedback. In theory this is faster as there is no dichotomy . In practice… I have yet to see this work well.

Granted, agile requires sufficient organizational maturity with the new artifacts, events, and roles – Product Owners able to own the backlog, empowered and knowledgeable enough to detail requirements and decide on priorities.

But I haven’t seen many Product Owners like that. Plus, with increasing complexity of the business landscape and progressing specialization, they simply cannot be know-it-alls, right? Even having sufficient business acumen, they won’t be able to drill down to technical levels detailed enough to provide a sound basis for development work.

How do we deal with this? From my perspective this is Agile’s uncharted land, that’s where “there be dragons.” Pre-sprints, parallel analytical sprints are just means to patch this up. The issue possibly requires several “whys” before we reach the root cause. My bet is that complete functional requirements are a necessity that cannot be neglected, and that they should form a response to whatever the business requests. Having agreed functional requirements we can expect viable “work packages” which can be decomposed, estimated, and developed with a higher degree of accuracy.

Backlogs or schedules?

“The schedule model simulates distinct scenarios and situations that predict milestones and completion dates according to the project’s actual and future data input by the project team. It is an important tool used for communication and managing stakeholder expectations.”

From Practice Standard For Scheduling, third edition, PMI

What do you find better? An ordered stack (a backlog) or a sequence of actives of varied length (a schedule)? Agile advocates the former, with waterfall we got used to the latter.

It’s easier to move items up and down in a stack. Rescheduling takes more time as you have to maintain logic (dependencies). On the other hand, a schedule allows us to see how activities relate to each other. Based on estimates – which are part of any schedule by definition – one can easily tell when to expect what. Of course, with relation to time a schedule is only a prognosis. The sequence in a schedule, however, provides value by itself – allowing the involved to see how tasks refer to one another. A work organization tool. And a useful one at that.

Lists focus on work in progress.
Schedules focus on relations and dependencies.

Lists draw attention to the work at hand.
Schedules show us how late we are, in addition to the above.

For a one-man band a list is fine. That’s my view. Where there’s teamwork involved, I prefer a schedule. And so do my customers – when asked, I can instantly tell them not only how much work remains (same goes for backlogs), but what the estimated duration is, and what the key milestone dates are.

I am in favour of new approaches. Sometimes a new approach is just a stepping stone towards something better. Better than schedules.