@Jared Dolich and @ArunManickam thank you for the responses! Regarding use cases, at my previous firm my primary focus was on FP&A (across numerous industries) and S&OP (e.g. demand planning, production planning, MRP, etc.) solutions. At my current firm the focus is on FP&A for financial services companies. Project deliverables at my previous firm included user stories with acceptance criteria and test scripts, which would be created by the client and tracked via a project management tool (e.g. JIRA or TFS). At my current firm we have those same deliverables but also a traceability matrix. Some online sources stated that traceability matrices are typically not included in Agile as one is typically covered via the user stories and test scripts. Overall, I feel the traceability matrix may be redundant to normal Agile, but to your point, perhaps there is a benefit to having it on more complex projects. Regarding using the Anaplan Way application from AppHub. At my last firm we used a separate project management tool because the firm implemented other services outside of Anaplan. This would enable a standard approach to track projects across multiple practices. At my current firm, typically the client dictates we use the client's existing project management tools. I agree that the Anaplan Way application would have some good tips and tricks to use, and that having the client update their project deliverables in the Anaplan Way application would give them more exposure to Anaplan and hopefully shorten any learning curve time. Regarding creating user stories in Power Point. I've seen projects with 100+ user stories, so I feel like a project management tool like JIRA or TFS would serve the same purpose as Power Point. On average, how many user stories do your projects have that you would then create in Power Point? Speaking of user stories. It'd be nice if Anaplan provided standard user story templates understanding that they will cover 80% of client requirements and there will always be another 20% that will have to be further defined during requirements gathering with each client. At both firms, I've observed user stories always being created from scratch and many clients asking if there are standard user stories that we can start them off with. I myself have attempted to draft standard user stories and garner feedback from my broader teams to supplement those as needed. I am cognizant that many firms are trying to establish their own value proposition to prospective clients, but for example, headcount and opex planning are relatively the same regardless of the industry or size of a company. For that, I think there should be standard user stories similar to the scoping scripts that Anaplan provides.
... View more
Hello, I'm trying to leverage your post to sum Weeks into 13 4-Week Periods. Background: Client would like a 13 4-Week Calendar beginning week of 1/6/2019 to 1/12/2019, which I already confirmed Anaplan's native 13 4-Week Calendar options (Day nearest end of Month) and (Last Day in Month) does NOT allow. Attached are a couple of screenshots of the direction I was going after reading your post, but did not have success. Would you be able to go into more detail for bullet "c" under Option 1? I got a bit lost at this section. Also, would you be able to clarify bullet "1" under Option 2 how you would map Week 1, Week 2, Week 3, Week 4 to Month? Replacing my Periods with normal months (for sake of example) based on your instructions I would do the following: List Member/Property Jan/Week 1 Feb/Week 2 Mar/Week 3 Apr/Week 4 However, I would need the following to occur: Jan: Week 1, Week 2, Week 3, Week 4 Feb: Week 1, Week 2, Week 3, Week 4 Mar: Week 1, Week 2, Week 3, Week 4 Any screenshots you can provide for you solution would be much appreciated! Thank you!
... View more