development Questions

I would like to get some expert opinion on the following product environment in terms of story writing and story slicing. Suppose if we have an enterprise product and many clients would be onboarding to the product in different timelines of deadlines with customized extra features than the basic product. As many clients are getting onboarded with more unique customized features and the overlap is in place, the Product owners are getting challenges in writing the story which enriches the base product that fits our system and slicing the stories into smaller units that fit into the 2-week sprint for the clients. What would be your suggestion or approaches on these sort of situations to address the story writing and slicing challenges?

By James Gray - April 28, 20201 Answer

Calling all software development project team members having Daily Stand-Up Meetings (DSMs).

My name is James Gray and I am mature student studying an MSc in Project Management at Solent University. I am undertaking research into how productivity can be affected by the start time of the Daily Stand-Up Meeting (DSM) within software development projects. I would be most grateful if you have the time to assist. All responses will be anonymous and the survey should take between 5 – 10 minutes.

To participate, please click this link https://sprw.io/stt-8a1c76

If you have any questions please do not hesitate to contact myself, James Gray ([email protected]) or my dissertation supervisor Dr Paul Summers ([email protected]).

how many userstories  based on story points  and  tasks calculated   for the sprint 

 

Agile product management aligns the Product,
Technical and Marketing teams towards building customer-centric products faster
with a possibility to refine the product scope based on the market conditions.

 

 

 

 

Reviews do allign closely with the agile manifesto, but what kind of metrics can be effectively related for Agile development?

I'm desperately looking for a bit of help! We are a small scrum team who recently turned agile (yay). The previous pm manager preferred using time estimations which was easy for pm's, not the agile-loving dev team. I want to teach my team how to switch to story point estimation and the major concerns of the team are - How do we explain cost to clients per sprint using points? Do we just take the budget total, divide into sprints (based on hours in a sprint) and cost this for a big project?

 

I have a very reluctant team so any help would be greatfuly appreciated!

 

K

 

Should stories be kept in place of requirements to provide permanent system documentation or should a functionally organized set of requirements be maintained as this documentation.     Either way, I am trying to figure out the best way to maintain a description/model of the system being maintained that is understandable to non technical and technical staff and provides a starting point for analyzing future changes to the system.

By richard semock - October 18, 20151 Answer

Previous conferences of Star West and the agile methodology in general have accepted the concept that testers and programmers are both subsets of the developer category. Is this still the accepted definition or are programmers the only team members that are considered developers.

By derrick bell - October 1, 20151 Answer

We are migrating a slew of reports. I'd like to apply agile methodology for this process. I would you recommend I proceed?

Can we really get good insight,  while  asking certain questions on agility, how it is practiced etc from agile team menmbers.

Pages

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.