Pros
• Highly complex subject matter hinged on retail pricing and complexities, if you are into number-crunching and numeric problem-solving, look no further. • Supportive software devs and QAs.
Cons
If you are an analyst, avoid at all costs. Here’re a few reasons why: • A smart, but extremely ruthless Scrum Master with zero capabilities in the emotional intelligence department. • Arbitrary deadlines. • A cut-throat, sprint-driven cadence with no breathing room for either skill-development or even a few hours of downtown, puts a whole new meaning in the concept of a sweatshop. • A management duality: do not expect to report to a Scrum Master who’s hiring you, you’ll report to Product Owner instead [fun to work with], but the two of them will continue to set forth conflicting, often mutually exclusive priorities; plus throw in the usual chaos of an unstructured, disorganized Scrum environment. • At this outfit, Agile methodology is not a methodology, it’s a religion: expect to duplicate your user stories both on an electronic Kanban board and (!) on the whiteboard, including any and all updates / ticket movements [& don't dare mention the concept of effort waste..]. • Forget about Visio, and any of your usual tools: you won’t be cranking out anything but an endless conveyor belt of user stories; client visit, customer meetings? Cross it out, too. • Should you choose to accept this mission regardless, at all costs do not mention that Agile metho is yesterday’s news, or forget about rapport with your key stakeholders. : -))
