Meetings are an intrinsic part of professional life. Meetings provide employees the opportunity to share ideas, network, improve their understanding of each other, and update employees and management alike on new developments.
However, when meetings are unplanned, they disrupt the entire work environment. Without a set meeting agenda, it is difficult to know whose attendance is a must for the meeting to be a success. Do you need the large conference room or the small one?
When you think of feedback at work, those yearly assessment and feedback forms flash across your mind. Although these annual performance reviews are helpful, it can also be helpful for managers to look beyond them.
Employees want their work to be recognized. They want to know how they’re doing and if what they do is effective enough.
Much like the practice of enterprise software delivery itself, traceability is complex and fast becoming one of the biggest technical headaches for organizations worldwide.
It’s easy to see why. Think of all those concurrent product lines. All those evolving features. All that mutable product information that specialist teams create and depend on during different stages of the process. Think of how the essence of Agile means requirements constantly evolve from backlog to deployed.
Remember the time you were sitting in the university lecture about staying focused?
The hall was full of students, all attentively listening to the energetic instructor. He really knew what he was talking about — or at least it seemed so.
Business focus has changed today from process-centric to customer-centric and value-centric. The key priorities are faster time to market, improving efficiency through automation, providing real value to internal & external customers in order to stay competitive and cost effective. The age of digital transformation and innovation demand businesses to change and adapt faster. There are various best practices and frameworks available in the industry to guide companies with a set of recommended processes for efficient IT Service Management (ITSM).
ITIL, COBIT, ISO/IEC 20000, CMMI, MOF, IT4IT, DevOps, Agile, Lean, SIAM, VeriSM.
In my previous blog post, I had a look at some of the award winners of DeveloperWeek 2018. In today’s post I will continue to overview them and the latest trends in development and modern IT world.
The reality of IT support is that engineers cannot avoid downtime. No matter how responsible managers are in ensuring regular maintenance and repair, incidents will happen. Sites will fill. Servers will fill up. APIs will fail. When these incidents do occur, it is important that IT teams are well trained and have the necessary equipment to ensure a rapid incident response.
However, incident response is not as easy as simply creating a check list for teams to follow. When incidents occur, there are often conflicting priorities between restoring availability and investigating the causes of the incident. For example, Security incident response teams and infrastructure teams operate with different sets of assumptions and priorities when resolving issues. If these separate priorities are not effectively managed before-hand, there can lead to the duplication of work, delays in handoffs, and faulty results.
Happy Monday, readers! I’m getting back on track with reader question Monday once again. No more excuses about bad web hosting issues.
Today’s question is about test driven development. Specifically, it’s about test driven development when you’re trying to get a team to do it—a remote team. Here’s the question (directed at me some time ago on Twitter).
Over the past year, I had the chance to be quite close to a significant project in terms of scope and team size. All in all, over 100 people were involved, with more than 60 working full time on the project.
Out of those 60 people, over 40 were involved in engineering, while the others worked as the Technical & Solution Architects, Business Analysis, User Experience Engineers, and Project Managers. Out of the 40 engineers, over 60% of the team was involved in mobile and frontend implementations while the rest were focused on backend and QA automation.
Ever feel torn between making a sensible decision and immediate gratification? You’re not alone. We like to believe that we’re rational and intelligent, making decisions in our best interest. Reality shows otherwise.
You might have noticed the term "Behavioral Economics" in conversation. Maybe you heard Richard Thaler won the 2017 Nobel Memorial Prize in Economic Sciences this past October. Or maybe you viewed our recent design thinking webinar with Damco and ADP.
