Hiring is difficult to do well, Johanna Rothman writes in her latest management myth piece. Because everyone who is looking to hire has a job, they think they know how to hire. But it’s not easy. You want to hire the best people you can who fit the team and the organization.
Holly Bielawa explains that being a a requirements craftsman means that you need to test your assumptions in real time while developing a product. Then you pivot as needed, change your business model as you learn, and constantly get out of the building and gather data to determine your minimally marketable product.
Kent McDonald writes that identifying objectives and the assumptions underlying them provides you a way to measure whether the result of your project will actually get you closer to what you are trying to accomplish, as well as the impact your various assumptions have on reaching that objective.
Charuta Phansalkar writes on the necessity of capturing and understanding requirements using agile practices. Agile, when implemented effectively, will ensure that the customer's voice is clearly understood throughout the project, which results in maximum customer satisfaction.
Joel Bancroft-Conners presents a survival guide for testers going to agile. Joel explains what happened when he had to make the switch from waterfall to agile. Welcome to the world of being an agile manager, in which your team is a top performer, doing more in the same amount of time as before.
Jean Richardson shares a story about how the idea of pervasive leadership can help you manage a successful project. In order to practice pervasive leadership, one must change one's mental model of "I" and "thou," act locally and think holistically, and enact empathetic stewardship.
Johanna Rothman explains the challenges and pitfalls of micromanagement. Sometimes, managers micromanage when they need information. In that case, it’s easier to create an information radiator rather than have the manager come running to you every thirty minutes.
The needs to improve the time to market of a quality product and adapt to a changing business environment are driving organizations to adopt agile practices in order to be competitive in the marketplace. However, a project team is bound to face difficulties if it is not trained on the fundamentals of agile. Read on to learn how to design scenarios for agile stories using a structured framework.
Technology-driven companies, regardless of size and scale, are facing the increasing need to ship better code faster while meeting business requirements. This requires collaboration and interaction among the traditional information technology infrastructure library (ITIL), information technology service management (ITSM), and development teams for a truly agile organization to emerge.
Terry Wiegmann writes about how Microsoft Word's features, like its spelling and grammar checkers, can help one identify agile smells—those signs that something might be wrong. While we may want to minimize documentation and the use of Word, we can mentally use some of Word’s features to sniff out some whiffs of smells.