Site Loading...
Your address will show here +12 34 56 78
Digital Transformation, Professional Development

Anyone who knows me, knows that one of the most important things to me is to be effective. Not efficient but effective. I believe strongly in the use of technology to streamline marketing and sales but think it’s important that tech knows its place. I even wrote a post way back when about how email is killing productivity.

That’s one of the reasons I like many of the agile principles and when I recently began exploring Stoicism, I realised that there is a lot of crossover between the two.

A quick primer – what is stoicism?
Stoicism is a school of philosophy that comes from ancient Greece. It’s primary goal was to enable its practitioners to lead a virtuous life, full of knowledge and governed by reason.  

A quick primer – what is agile planning methodology?
Now commonly shortened to just “Agile” – this is a set of principles or structures that you can use to help direct or steer a project. It started out life as a computing development methodology and is now used in all walks of life.  

Inspect & Adapt / Stoic Reflection

First off, what do I mean by effective? Basically getting the most valuable and important tasks done in the shortest amount of time, and not unnecessarily repeating tasks more than once. This leads me to the agile principle of Inspect & Adapt, or the Stoic version which would be Reflection.

There’s no way to make sure you’re using your time effectively unless you review what you’ve done in the past. Try to be objective and determine if the tasks you were doing were genuinely valuable to your business and whether you seem to be doing that same task time and time again. A great way to do this is in the swimming pool, where, unless you have your music with you, there’s nothing to hear but you, the water and your thoughts. A perfect opportunity for some quiet time.  

Automate / Dichotomy of Control

One of my favourite stoic principles is that of the dichotomy of control, recognising that there are a limited number of things you have complete control over and there is little point in getting upset or worried over things outside of your control. So, when you determine the tasks you are doing which are repeatable, work out the end to end process first, and document it before you outsource it. This will limit your exposure to future frustration because the person doing work for you will know exactly what you expect and therefore will have a greater chance of delivering.  

Team Spirit / On Seeking Fame


Agile is definitely not about the individual and neither is Stoicism. The former spends a lot of time talking about the collective value of the team to one another and the latter discourages practitioners from seeking to be well known as this ultimately leads to too much concern with what others think of us.

It’s a little like the 3 muskateers – All For One and One For All! Work with your colleagues first towards a common outcome rather than thinking of yourself.  


If you’re interested in learning more about Stoicism but want a gentle introduction, I’d thoroughly recommend William B. Irvine – The Guide To The Good Life. It’s an easy read and is full of lots of practical advice and examples. Or, if you want more practical advice on agile methodology, try out Roman Pichler – Agile Product Management With Scrum – it’s the first book on agile I ever read and was very helpful.

0

Agile, Product Management, Professional Development
Now that we’ve established what a product manager does, just how does that product manager prioritise competing requests that come from all areas of the business? In our mind there’s only one way to do this: Business Value.  

It’s important to note that business value doesn’t just refer to actual dollars brought in but to the long term value of the product and its users – all of which can easily be traced back to dollars, but it’s not just about sales!

There’s a common misconception that perhaps the way to make sure you get your requirement easily seen to is to be the best salesperson for that requirement. We reject that statement – strongly. It’s not about razzle dazzle, it’s about how valuable that feature is to the overall business.  

How do you assess business value?  
It’s not an exact science and it’s not expected to be, but it’s the best tool you have to gauge priorities in development. Take into consideration all angles:
– How does it tie back to the overall business and product vision?
– Is it a USP and something that will set you apart in market?
– What is the associated effort from the team to put it in place?
– Is it attached to a commercial campaign or will it drive user acquisition – how much of each is it worth?
– Are there other reasons you might consider doing it (to get an internal department on side for example)?  

Once you have all the answers to these questions it’s time to do some maths in your head. Add up all the pieces and then weight them relative to all the other requirements in your backlog. The ones that come out on top (have the biggest “bang for buck” so to speak) are the ones you do first.  

Now you continue to iterate on these calculations, always re-estimating and re-evaluating your bang for buck to make sure that your team is working on the items with the highest business value at any one time. By working in this way it may not always be obvious why you have chosen specific features (they may be hard to develop) or why you have said no to some features (when they are easy to develop but don’t tie back to the business vision) but you’ll always be working on the right thing.  

If you’re after a bit more insight into the overall agile product owner process, watch this video on YouTube.

Image Credit: Photo by bonneval sebastien on Unsplash
0

Agile, Product Management
A friend of ours used to joke that the name of this company should be Vertical Slice because of the number of times we’d say it in a given day and how we’re forever having to explain to new people just what it means. It’s an agile term and yes, I know it sounds like we’ve drunk the kool aid – because we have.  

So, just what is a vertical slice? Well it’s one way of describing a software development practise that can be applied to pretty much anything in life and it boils down to this: rather than developing different pieces of the puzzle in isolation, instead, work on making the smallest possible bit of the puzzle all work together end-to-end first.

For example, if you were making a trifle you would start with a very thin mould (thin slice) where you layer all the ingredients in on top of one another, leave it to set in the fridge immediately (where it sets much quicker because it’s not the full cake), then take it out, test it out and see what it tastes like (the customer response).  

mke-agile-032014-slicing-the-cake-user-story-decomposition-4-638
There are lots of advantages to developing this way. In the first instance, because you’re making all the layers of the cake work together at the start, you inherently reduce your risk of blowing your deadline by working with technologies that might be difficult to integrate. You identify problems much faster, thereby giving more time in the project for thinking of a solution (rather than the converse which would leave you at the end of the project rushing to make layers work together).  

Secondly you get to demonstrate a version of the end feature to your customer much faster, meaning you can learn from their feedback about whether this was what they wanted in the first instance and what you can do to improve the feature based on their actual requirements (not just what you think their requirements are).  

Thirdly, it gives you the option to launch the full product faster. You cut out wastage in developing features and functions that are not desired by the customer (no matter how logical they may seem to the feature team) and, if needed, you can launch a solution that makes a date requirement but doesn’t necessarily have all the bells and whistles that originally were envisaged. Meaning you get to market faster than your competitors.  

We could go on but you get the idea. Take your requirement and boil it down to the simplest possible variation. For example, if your requirement is that customers can login to your site, and the full version has login across multiple different types of accounts, start by doing login just with Facebook. Don’t style it in your initial story. Boil it back to the basic requirements: – A customer can login from X device, using X browser, via their Facebook credentials This will give you immediate visibility of any technology problems and allow you to pivot your requirement much earlier without having wasted valuable resource on design.  

*Vertical slice slide borrowed from Dave Neuman @ Slideshare
0

Link partner: slot5000 luxury333 batman138 dewagg idngg vegas88 elanggame bro138 bos88 gen777 zeus slot roma77 liveslot168 luck365 sky77 maxiwn138 harta138 qq1221 qqdewa qqalfa qqpulsa qq88asia qqslot777 roma77 pg slot habanero slot mahjong slot