Related Content
More Slack Time, Please! As we seek and achieve efficiency, we eliminate "slack"—purposeful time to allow our brains individually and our organizations collectively to create, think, reflect, analyze, contemplate, plan, learn, grow, and change. This story gives some ideas for building more slack time into your routines. |
||
Building a Testing Framework for Digital Accessibility Many mistakenly believe frameworks are applicable only to test automation because they provide easy test implementation, enhanced productivity for testers, and empower dependable quality for the product. However, accessibility also is a rich ground for frameworks to be built and leveraged. Read on. |
||
How to Make a Meaningful Apology Issuing apologies is often deemed a natural gesture, but how should apologies be made so that they are more meaningful? Good apologies thrive on honesty about the feelings, show genuine concern, and demonstrate fitting behavior. Anuj Magazine examines some recent public apologies that made the news. |
||
Planning Techniques for Estimating Projects Agile teams often use estimation to plan projects. There are many different methods, and which you choose should depend on the type of work, what kind of deadline there is, and your team. Matt Heusser explains some estimating techniques that can expand your options when planning a work effort. |
||
Are You Focusing on the Right Thing in Your Sprint Reviews? The role of demonstration in a sprint review often takes on more importance than it should, even to the extent that some teams refer to the review as a demo. By focusing on the demo you risk having the team do all the talking, rather than a two-way conversation between the team and the stakeholders. |
||
How to Succeed at Project Failure If you're bound and determined for your software project to fail, you're in luck: Naomi Karten has some advice for you. She'll tell you to set unclear objectives and unrealistic expectations, leave gaps in communication, and ensure a lack of resources and support. You'll be failing in no time! |
||
Who Is Responsible for Happiness? No one can take full responsibility for another person's happiness. However, a manager can create an environment in which a team can thrive, and that leads to happy environments. Being a servant leader means you don’t micromanage; you manage for outcomes. Is team happiness part of your culture? |
||
“Post-Heroic” Leaders and Agile Teams Self-organizing agile teams still need management, but they need a different kind of management from the autocratic style many teams in nonagile organizations have. A "post-heroic" leader is able to shift from an authoritative manner to a collaborative one as needed to optimize team performance. |