How to use Microsoft Feedback Client 2017 to get stakeholder feedback into VSTS/TFS.
Subscribe for more…
Why, How, What of Kanban – is a walkthrough of Kanban using a software delivery pipeline example.
A power packed hour of world class project management with Microsoft tools and technologies.
Cloud productivity and desktop tools to deliver modern agile projects as well as traditional projects.
What is Project Management? Explanations and demo examples using Microsoft tools like:
Side by side comparison of JIRA and TFS/VSTS for a typical Scrum project. High level comparison of the top ALM solutions for modern agile software development.
Also see – http://www.almbok.com
Subscribe for more…
Explaining the Application Lifecycle Management (ALM) concept and how it fits together in the modern world of Agile and DevOps.
For more than 20 years software development has been both my passion and profession. Many things have changed during this time and not all for the better…
Sometimes I miss the feeling of being in full control and understanding every little piece of the software from ideas to actual usage. In some sense it was easier before when this was expected from a software craftsman like me, to be able to deliver it all in one self, and to be the whole process and not just a replaceable gear that’s moving other gear without understanding the purpose. For me the completness is where the passion was created, the endless curiosity and borderless creativity was created from this spark, resulting in a lifelong passion for software development.
Modern software development practices seems to aim for the return of the completeness into focus for developers – ALM and DevOps. Regardless of the role we have in the team the feeling of being a part of the whole and not just an isolated part should be valued as it feeds the sense of purpose and nurtures curiosity, maybe even sparks passion.
Continuous innovation, feedback and improvements feed the lifecycle engine in continuous agility from planning to operations. Composed of persons, processes and tools to make it more predictable and deliver more quality software faster.
Gathered behind the shared goal of increased transparency and cooperation between all stakeholders involved in the software crafting process, making increased collaboration the key to success and sparking passion.
In the end it is the passion that rules the game.
Please let me introduce you to a Swedish word (“Lagom”) to describe the perfect balance. Not too little, not too much. Just right. That’s also exactly what projects are all about, to get the perfect balance of cost, scope and time to produce a lagom quality in the result.
Being from Sweden myself lagom comes naturally, the word is positively charged and lack a lagom English translation. Lagom for me may not be lagom for you, hence lagom can be very complex to get right given many estimation parameters, just like a modern software development project.
So how do we deliver a lagom software project today, mixing both traditional and modern concepts? I would argue that managing stakeholder expectations is part of the key to lagom delivery, but maybe more importantly is that we have trust and clear communication. If we micromanage resources we don’t trust them, this often leads to obfuscation and not to lagom.
So how do we deliver high trust and clear communication, and manage stakeholder expectations? We use tools and technologies that support, integrates and facilitates the ambition. Because each project is different the solutions has to be flexible and lagom adaptable to continuous changes. But even more important is that we are humans, we all have different history and experiences that aggregates into potential human integration risks and different viewpoints on lagom.
So how do we manage human resources and human integration risks? We don’t. We aim for self-organizing teams and focus attention on the positive risks and synergies when people are coming together. This is a big part of the trust, we do best to trust our fellow humans and the ability to deliver and to collaboratively solve the issues. We benefit from clear and transparent communication between stakeholders to get the feedback needed in order for lagom delivery.
Friends, this is how I define lagom.
Hello, Friends! Are you interest in delivery of quality software in less time? Let me introduce a new experiment I’m working on to help close the gap between Business practices and Software Development practices – ALMBoK.com.
Application Lifecycle Management (ALM) defines how a software application is managed from conception, through its creation and deployment, to its eventual retirement. ALM is made possible by tools and technologies that facilitate and integrate requirements management, architecture, coding, testing, tracking, and release management. ALM recognizes that the requirements are evolved based on business needs or ideas for new opportunities. Applications are the foundation from which business processes are executed.
Modern ALM and DevOps practices enables integrated and optimized processes that provides the agility needed to quickly take advantage of increasingly faster paced business demands.
The Body of Knowledge (BoK) provides the insights to improve business and development processes via knowledge areas and groupings of knowledge articles (disciplines, methodologies, products and tools) from both internal and external sources.
The ambition of this free knowledge base – ALMBoK.com – is to cover the high level perspective and to serve as your guide in Application Lifecycle Management.
For more detailed information please visit the site – www.almbok.com
Här kan ni finna information kring mig och de saker jag tycker är intressanta, såsom projektledning, applikationslivscykler, gruppsamarbete och så klart en hel del som berör systemutvecklingsprocesser.