Pretty much nothing, would be the short answer to the question above. Those are however very popular as content requests that I receive (about 1-3 per week, on average) for the podcast, where some listeners are asking to clarify what Cryptocurrency is, in simple terms. I feel like the Agile “news” are a bit slow by definition – we are just all doing our little jobs out there, championing the cause, don’t we? – so decided to accommodate this request and invite a guest on the show this week…
After what felt like a long review from Audible.com, I can finally see the 2.5 hours of my audio version of Get Hired As Scrum Master book appearing in Audible search engine.
In addition to Audible, it should be available (or appear shortly on) Audiobooks.com, Hoopla, Libro.FM, Overdrive, BookMate and at a few other online audio book retailers. This is a huge milestone for me, and I’m genuinely happy to share these news with you – my occasional blog visitors and podcast listeners, who already are consuming audio content I produce.
It is interesting that research shows that our consumption of text-based eBooks is on a rapid decline now, with some numbers suggesting as much as 30% drop of eBook purchases across major online retailers including Amazon in 2017…
After a long break I’m back to posting a quick summary of the latest podcast episodes, for those of you who prefer “show notes”-like summary instead of (or in addition to?) jumping straight into audio.
On this 24th episode of the Lean and Mean Agile Podcast I’m reviewing Atlassian JIRA – an extremely popular Agile Collaboration tool, at least among the Australian companies that deal with development and delivery of Digital Products.
What makes JIRA great? What are its defining high level features?
As some of you might have noticed, the look of my site changed a few times over the past couple of weeks. And (spoiler alert!) these changes are probably not over yet…
What’s happening is that I’ve been a lot more into production of content other than direct blogging, even having a luxury of web development skills, this web domain and fully functioning WordPress installation. You’d say – “mate, you just ought to write something as a blog here now and then!” – and you know, after long deliberation I actually agree with you. I should.
On this podcast episode I’m tackling the topic of cross-functionality in Delivery Teams, as well as the confusing term of T-Shaped people.
The meaning of cross-functionality is rather simple – it’s when ideally everyone on the team can do anything, within the predefined requirements of the full range of skills required to create the Product the Team is ultimately building.
T-Shaped Team members however could sound very confusing and almost disturbing. While in essence the term is also rather simple and works on the theory of us being able to get proficient with one (or very few) core skills, while aiming to develop familiarity and at least base level of skills covering broader range of relevant areas. So that core “deep” skill becomes the vertical line of the “T”, while the broader range of more “shallow” skills is represented by the horizontal top line.
More about this on the actual episode after the break…
As discussed on the recent Podcast Episode #8, there’s no one size fits all approach to constructing Kanban boards.
If you embrace the core principles of Kanban, you should start with visualizing your current process, or Flow of Value through your specific System. Your Kanban Board should be designed to reflect that flow of work (producing Value in the end) as closely as reasonably possible.
If you had to remember one thing about Kanban, it probably should be – visualise your current flow of work, and then seek ways to improve it as time goes by.
Hi everyone, just a quick note to anyone who would rather listen to an audio material rather than consume online courses or YouTube videos – I’m happy to announce the launch of Lean and Mean Agile Podcast (solo show with yours truly), dedicated to all the main topics surrounding Agile Values, Practices, Frameworks and Mindset itself.
I’m starting with the real basics, laying the foundation for potential newcomers into our space, and will plan to expand into more tricky areas of Program Management with Agile Delivery in mind, bringing occasional guests on the show who would be able to contribute to topics we will be discussing.
Podcast is weekly, 15-20 minute show, available on SoundCloud, Stitcher, and iTunes – just click on the widget banner on your right, and subscribe to show your support. Cheers.
Applying for an Agile Delivery role such as Scrum Master? I’ll give you some basic tips on how to prepare your Resume (or “CV”) for easier digestion by the Recruiters or Human Resources of the hiring company, so that you have higher chances of making it into the group of short-listed candidates…
Having some sort of work experience in the relevant area is crucial to success when applying for any of the present day Agile Project Management or Delivery roles. Situations where someone would give you e.g. a Scrum Master role just by looking at your fresh CSM or PSM certification are extremely rare, and usually contained to side-shifting within your own company, where basically people know you, and want to give you a chance. As fantastic as those rare opportunities are, we should focus on the open competitive market conditions, where you walk into the door of the potential employer as a fresh applicant, with no history with that new company. So how do you convince them to hire you?
What are “Hybrid” roles you ask? It’s those where recruiters or the companies offering actual jobs try and combine responsibilities of multiple Agile Delivery roles into one position, creating those – sometimes rather weird and unproductive – hybrids. It’s roles like Project Manager/Scrum Master (PM/SM), or Business Analyst/Iteration Manager (BA/IM), and many other combinations where paying attention to what your potential employer is asking for would be crucial for you to be remotely successful in that role, as well as staying sane! 😉