For me, writing has four main parts: researching or deciding what to write and organizing it, writing, editing, and publishing. You might think of these steps as analysis and design, coding, testing, and release. I like to keep my writing chunks small so that my editing occurs soon after my writing. Small chunks also means […]
In Part 1, I described your job search planning. In Part 2, I discussed what you can do to help your resume. In this part, I’ll talk about the interview. Any candidate needs to prepare for the interview. If you are worried about ageism, consider these tips for these challenges: Specify your value, first to
In Part 1, I suggested five tips for the “older” job-seeker. In this part, I’ll talk about what you can do to craft your resume. The problem is this: you don’t have to be too old to have ageism happen to you. The older people perceive you to be, the more ageism you will encounter. Those
About a year ago, I wrote “Hiring Trap: Don’t Hire Anyone Older Than….” Unfortunately, ageism is still rampant. If you are a candidate over the age of 40, you have encountered ageism. If you are also unemployed while you are looking for a job, you might feel as if you are up the proverbial creek.
Build Your Agile Leadership In your organization, agile has helped your teams improve their value delivery. Although the teams retrospect, you expected more improvement. You think your agile journey might be stuck. Maybe it’s time for you to build a culture of agile leadership. Tip 1. Make your work transparent. Do other people know what
In Part 1, I discussed the agile project system. In Part 2, I discussed the tester’s job in agile. In Part 3, I discussed expectations about documentation (which is what the original question was on Twitter). In this part, I’ll talk about how you “measure” testers. I see a ton of strange measurement when it
In Part 1, I discussed how an agile approach changes testing. In Part 2, I discussed how the testers’ job changes. In this part, I’ll talk about expectations. Since the developers and testers partner in agile, the testers describe their approach to testing as they work with developers on the code. (This is the same
Last week, I attempted to have a Twitter conversation about agile and testing. I became frustrated because I need more than 140 characters to explain. This is my general agile picture. For those of you can’t see what I’m thinking, the idea is that a responsible person (often called a Product Owner) gathers the requirements
In Part 1, I discussed the project system of agile. In this part, I’ll discuss the need for testing documentation. In a waterfall or phase-gate life cycle, we needed documentation because we might have had test developers and test executors. In addition, we might have had a long time separating the planning from the testing.
I spoke with a potential client last week. She said, “I’m waving the agile flag. But no one cares.” I wrote a Pragmatic Manager to sort through what I wanted to say to her. Read it at Feeling Alone on Your Agile Journey. If you feel stuck in the middle, or you’re alone, or you