Velocity Chart in Rally [closed] - agile

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I am working on a project to pull out data from rally and create a velocity chart.
I understand the REST Web Service APIs to use are Defects, Iteration, Hierarchical requirement and Iteration cumulative flow data.
How are the calculations are done to calculate the velocity per iteration for a particular project?
What data is required and how can it be achieved? Right now I'm able to pull plan estimate of all accepted user stories and total plan estimate.

I wrote an app recently to calculate velocity. I used the story points of all accepted stories/defects in a time period (iteration/release). My numbers ended up matching what Rally had for my velocity, so I believe that is all it takes.

Related

How to map Activities to Tasks in a User Story Mapping session [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
In a user story mapping session, we should start by Identifying the different user types, then their goals or outcomes (represented on the map as activities), and the goals or outcomes of the company (represented on the map as versions or releases).
So for me it makes sense to try to deduct backbone tasks from user activities.
But in his book, Jeff Patton has an example (Everyday life) where he does the opposite, he first list all the tasks, then group them by higher goals or Activities.
So I am confused. From top goals to tasks, or from tasks to top goals ?
From top goals to tasks if you want to deliver fast.
Doing "As an HR manager I want to see turnover reports so I can better focus staff retention initiatives" first instead of starting with (e.g) a "Build CI/CD pipeline" task is the way to go.
That's because it eliminates waste and invites iterative problem solving: "At a minimum, what do we need for continuous integration/development so the HR manager can get her report?" is a great starting point. Go live on production with that, than beef up CI/CD as needed for the next story.

Divide similar users into social groups [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I have a dataset containing general consumer reviews of products purchased by users. The dataset also includes the item name, price, stars given by the consumer to the product. Please suggest me a way to approach this problem so as to make clusters of similar users using the given information. As of now I'm extracting keywords from the reviews column. I have shared the dataset preview.
in my opinion you should try to use some text clustering methods. Probably, the most informative value in your dataset is a review part. So at first you could try to change representation of your input data (using e.q tokenization, word embeddings) and then use some clustering methods (DBSCAN, Kmeans, tsne) to show if there exist some distinction between these grousp.
Good starter should be:
https://www.kaggle.com/karthik3890/text-clustering

Is this approach 'agile'? Separating use-cases into sprints/iterations [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
This may be a weird question and please bear with me, I am completely new into this.
I have a list of 20 requirements (use cases) which I received from my client. With him, I prioritized this list of requirements (1 highest 3 lowest). I wrote for every requirement a use case scenario (rather than user story). I also have a use case diagram and some technical designs (class diagram, database diagram).
Now, my plan is to separate this list of 20 requirements into 5 sprints. Each sprint lasts one week.
During every meeting with my client, I can show the product with 4 new use cases implemented. If one of them isn't finished, I move it to the next sprint and my client can request a change during this meeting. During this change, the specific use case diagram and classdiagram/database diagram may be changed.
Is this considered to be Agile? (Even though he gave me the full 20 requirements from the start of the project)
Agile is sort of a big tent, but I would not apply that label to the process you've described. You are describing lots of upfront design work and a full specs up front. The schedule assumes all the req take the same amount of time to implement, thought you acknowledge that it could slip.
The primary agile feature I see is the tight (weekly) feedback loop with client.
I recommend trying on http://pm.stackexchange.com.
This is not considered as Scrum:
- Schedule is prefixed (5 sprints).
- Velocity is prefixed (4 use cases/sprint).
- No scrum ceremony is followed as such.
- All requirements are given upfront.
Please refer - https://www.scrumalliance.org/why-scrum/core-scrum-values-roles

Graphic to check for complete separation [closed]

Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I need to check for complete separation. I am using SPSS and need to know what steps I have to take to get the grahpic on this site. Can someone help me?
SPSS does not provide that probability curve (SAS and Stata can do that). However, plotting the 1/0 outcome against the continuous predictor, and observe how the two horizontal data lines overlap may be enough to give you some hint.
If you have enough data, you can also first separate your data by different groups (for example, 10 equal groups split by your continuous predictors), and the compute each group's mean (aka probability of "yes" to outcome), and join the points. That line should approximate the curve in the illustration you provide.

Effects of sound multiplication [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
What are the effects of multiplication of two different sound? An neither of them are constant, like two different songs, or one track of instrumental and one of vocals.
A simple Google search came up with this:
http://crca.ucsd.edu/~msp/techniques/v0.11/book-html/node77.html
Did you search for it at all?
But basically what happens is you end up creating an envelope where the second acts as a "coefficient" of sorts.
You also end up with a reduction of sound levels (since a decimal times a decimal is less both of them), so you'll need to amplify the signal a bit to retain volume.
The page I linked gives a lot more explanation and has a lot of the algebra needed to write up a code to implement it. Look there if you have any more questions.

Resources