Rules: >You start from the last letter of the term posted previously. >In case, more than one terms posted with same letters (concurrently posted), you start with the latest term. >Only PMI-ACP® Terms in this relay. >A term may include multiple words. >Acronyms are fine. please include the expansion before the description. >Your term needs to be followed by a short description of the term. >No successive posting of term by the same member. The below one is fine. member A: --------L member B: L----- --- ----D member A: D---- ------ ---- > If you don't get a term starting from a particular letter(last letter of previous term), feel free to start from the next letter. e.g. previous term - buzz, if you don't get a term starting with 'z', you may start with 'a'. (Hoping this rule will be rarely used.:) >End date of game: No end date. Till the game goes on.
Markus KopkoAI Enabler for Project & Program Mgmt | Founder PMotion.ai / The PM
AI Coach| PMotion.aiHamburg, Hamburg, Germany
no prob Demtrius
Sustainable Pace -
To set your pace you need to take your iteration ends seriously. You want the most completed, tested, integrated, production ready software you can get each iteration. Incomplete or buggy software represents an unknown amount of future effort, so you can't measure it. If it looks like you will not be able to get everything finished by iteration end have an iteration planning meeting and re-scope the iteration to maximize your project velocity. Even if there is only one day left in the iteration it is better to get the entire team re-focused on a single completed task than many incomplete ones.
Working overtime sucks the spirit and motivation out of your team. When your team becomes tired and demoralized they will get less work done, not more, no matter how many hours are worked. Becoming over worked today steals development progress from the future. You can't make realistic plans when your team does more work this month and less next month. Instead of pushing people to do more than humanly possible use a release planning meeting to change the project scope or timing.
Fred Brooks made it clear that adding more people is also a bad idea when a project is already late. The contribution made by many new people is usually negative. Instead ramp up your development team slowly well in advance, as soon as you predict a release will be too late.
A sustainable pace helps you plan your releases and iterations and keeps you from getting into a death march. Find your team's perfect velocity that will remain consistent for the entire project. Every team is different. Demanding this team increase velocity to match that team will actually lower their velocity long term. So whatever your team's velocity is just accept it, guard it, and use it to make realistic plans. Saving Changes...
Love can sweep you off your feet and carry you along in a way you've never known before. But the ride always ends, and you end up feeling lonely and bitter. Wait. It's not love I'm describing. I'm thinking of a monorail.
