Development and organizational learning
Why should an organization learn?
Reality and trends in the industry are changing at a dizzying pace. Some of these trends are just fads that do not contribute much from an organizational point of view, while others are worth implementing into the organization. Why? Because they can be a response to a company's needs, such as when an organization has grown and its processes need to be adapted to its new size. Changes can also reduce costs or increase the value of a service or product. Sometimes, they simply fit the company's vision for growth, or the market and customers demand it.
How do you teach an organization?
An organization is made up of people, so the question comes down to how to teach new skills to the individuals who comprise the organization. There are at least a few ways to achieve this. Training seems like the most obvious method, but knowledge that is not consolidated in practice after training is difficult to implement permanently in an organization. In my opinion, there is a more effective way of learning, which is learning by working with someone who has the skill. Most of us have seen this in our organizations, either by learning something ourselves in this way, or by teaching it to others. When management hires a person or company who has a key skill for the organization, and after some time, even if the person or company no longer works for the organization, the way of doing things and the skills remain. Recently, upon leaving the organization, I realized that there was more of me left in the organization than just the habit of walking up the stairs. And I don't just mean the development of the product I worked on. I mean processes, skills, and habits.
What can your organization learn from hiring Craftspire?
At Craftspire, we are keen to share our knowledge and skills in the broad field of agile product and software development, including both the product/business side and the strictly technical side:
use of good practices in your SDLC (code review, TDD & test-first development, CI/CD, documenting changes)
working on the product (discovery, defining value (start with why), working with MVPs, validating ideas)
working with requirements, their priorities, and their clear formulation
collaboration between stakeholders and the wider business and IT.
Importantly, with this approach, the knowledge and skills remain with the organization, because after all, you are hiring us for a specific project.
