You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
- thanks for your answer. I think in at least one case we are gravitating towards your last suggestion when we can. We have to think about how the off-to-the-side project by a single person doesn't derail a lot of the community ownership we have developed, but that seems to be worth it.Kris– Kris2011-06-01 21:28:59 +00:00Commented Jun 1, 2011 at 21:28
- 4If you are going to do that with a few people then just pay attention to how it affects the morale of others who are actually doing project work. They may feel you are giving special advantage or preferential treatment to people who complain.maple_shaft– maple_shaft ♦2011-06-02 11:03:46 +00:00Commented Jun 2, 2011 at 11:03
- Also, take great care to keep everyone engaged and communicating with each other, even if a few members are working on trailblazing. Examples: everyone attend the daily and planning meetings; the trailblazers should give an overview of their work and demo their results regularly (maybe less frequent than the Agile team, but still bi-weekly or monthly), keep the team leads informed of the impediments seen by the trailblazers (so the latter don't keep pursuing a dead-end). Disclaimer: I am exactly this kind of person and I think it can work out really well.rwong– rwong2014-06-07 19:16:26 +00:00Commented Jun 7, 2014 at 19:16
- 1On the other hand, if a company's development workforce is primarily composed of trailblazers, and it is their consensus that they won't adapt to an Agile development style, then maybe this workforce will have much difficulty adopting Agile development practice. Other approaches need to be sought. As trailblazers love experimentation, new hires need to be brought in to take care of the productization needs so that the company can monetize its R&D.rwong– rwong2014-06-07 19:19:22 +00:00Commented Jun 7, 2014 at 19:19
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you