El prisma lean-agile
To understand the reasoning behind the lean-agile prism, I will first share with you a recent story with a client I advis.
A luxury hotel recently ask me to evaluate the operations automation software they had develop. The system develop was quite comprehensive and includ aspects such as room service management, telephone activity, front desk, parking, laundry, safe deposit boxes. The systems manager, let’s call him Pro, was the creator of the system—literally—and he show me what he had done up to that point.
He aptly show me the functionality in the places
where the actions were carri out. For example, he took me to the front desk to show me the operations carri out there and how the system was us. The tone of his voice during the explanations chang armenia phone number library from pride to frustration and vice versa. Pro eventually said: “I don’t understand why employees make so many mistakes when using the system if everything is clear, and I also don’t understand why they call me at all hours of the day and night with unnecessary questions.” Pro was right that most of the problems did not really what is the difference between exist, and that most of the problems were due to human error.
His belief was that staff did not know how to use computers properly
My conversation with Pro that day start in front of a whiteboard in a boardroom, where he drew a diagram showing his automation strategy, including what has already been done and the outlook. His plans were reasonably sound from a technical point of view. Some aspects that I didn’t like were the reactive belize lists approach and the lack of attention to quality, as well as the lack of attention to users. Pro believ that his systems have add a lot of value due to the high amount of automation and the reliability of the code. However, users were not satisfi. Something was missing.
