We use examples on a daily basis. This publication provides a motivation to giving examples, especially in a visual form with a purpose to clarify certain issue. Explaining through examples bases on comparisons. The visual approach is strongly preferred because of the visual nature. The nature creates an opportunity to instant consumption of the content. Simple picture can provide more information than tons of words. Some visuals require comments, though. We consider here both the positive and the negative power that pictures can bring.
Together with two colleagues from SAP hybris we’ve elaborated and provided a lecture with labs about Agile for students. We’ve been asked to deliver the lecture and labs covering practical Agile issues for students from the Silesian University of Technology. We advertised our session as: Agile – how it really works? within the Hack Your Career activity.The purpose was to take into consideration Agile area from the practical point of view.
The goal of this article is to put emphasis on introducing Tech Debt identification and evaluation into development process on a daily basis. We notice that not every Tech Debt symptom makes a real debt worth to work on. There’s also addressed how Tech Debt is defined in quality expectations and how it’s correlated with Business Value.
This discussion is about respect in attending work related meetings. The undertaken consideration and hints may not work properly for private meetings. There’re taken into account organization’s meetings including plannings, retrospectives, reviews, standups, all hands meetings, presentations. They apply to both onsite and remote venues.
This is one of the most inspiring and efficient books I’ve ever read. Agile mindset lives on every page of the book. The publication touches many PM areas and puts an agile cover on them. This might be a challenge to finish reading the book with no understanding the agile approach in IT projects. Agile thinking is revealed sometimes explicit, sometimes more subtle throughout the whole content.
The cooperation with external people may be a challenge for agile teams. These people are often experts working as a smaller or bigger part of an agile team. As long as an expert is not a full-time and dedicated team member involved in development lifecycle, this is a challenge to organize common work in a consistent way. We consider factors making the cooperation inconvenient. There are also produced common working agreements supporting organization of mutual collaboration.
Companies are getting bigger, projects do so, and a need of scaling grows. The purpose of this post is focusing on aspects of building agile scaling scheme in an organization. There are taken into account communication and integration aspects. These aspects are often not properly executed or neglected at all. They are in fact inevitable factors in achieving scaling goal.