I can speak about my part of the organization under my leadership with is the engineering team. A reputation really depends on who do you talk to and I would consider it to be always an opinion. It is not possible to guarantee to treat people with no mistakes and i am sure that I have done many of them. However, the most important thing is learning form past mistakes through listening to people closely, continuously incorporating feedbacks and working on them and responding with empathy.

---

I am really grateful to all people who helped in shaping up our culture, building our products some decided to move and evolve in their career and some decided to stay and fight amazing challenges. Even a painful experience is a good experience that contributed positively to shape our culture. That is the Xceed way. We never claim to be perfect but guarantee that we keep improving. But, also it has to be clear that we never violated a legal binding that was held with any employee and that is fundamental and core value that we believe in.

View more

So let me explain a very fundamental concepts about software documentation and software planning.

---

We plan (or design they are the same) for software to ensure that we end up with (1) building the software "the right way" and (2) cater for change by having a good design.

---

We document software to ensure that we are (1) building the "the right" software and again (2) be ready for change.

---

Now, how does agile overcome these two acts "planning" and "documentation" that might take you away from the essence which is building software? The answer is through (1) a team that is technically sound (building it right) and (2) incremental value (building the right software). Which means the the software is well written so that it doesn't need documentation, the team is technically strong so they know what they are doing keeping the whole picture in mind all the time and deliver incremental value yo the custimer.

---

Finally, back to your question. If you understand why planning and documentation happen and how agile looks at them, then you need to show the value of agile through real work not only words and show why we don't need a plan and documentation.

---

One final note, agile doesn't forbid planning and documentation for good, it just elemenates the unnecessary parts of it. However, you will still need product planning, features documentation, user documentation that will happen outside of your agile cycle.

---

wow. thank you for this great question. You squeezed my mind.

View more