development Questions

 

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.

By Paul VII - September 17, 20145 Answers

There are many paid resources out there but I do not feel it is always necessary to pay.  The scrum guide is good but short.  This one I can recommend: http://www.freescrumebook.com

 

What are your thoughts?

Unless I've misunderstood the principle, agile sprints are about layering on features until you arrive at some final release.  

But software can become unwieldy complex and choosing the right data structures and class patterns, for the application, is crucial - isn't it?  

So, how can you decide on the right data structures and classes and patterns, at the very beginning of the process, if in the first sprint, you are only dealing with a few of the overall application features?

Do you continually refactor and re-write as new feature-information is presented? Or is there some overall application design architecture happening up-front?

BTW, I'm not a formally-trained computer scientist, or software developer.

In my research study, I need to identify the list of key features of user story management tools that can be used to support agile development. So far, I identified the following general groups of features: User role modeling and personas support, User stories and epics management, Acceptance testing support, High-level release planning, Low-level iteration planning, and Progress tracking. Each group contains some specific features, e.g., support for story points, writing of acceptance tests, etc.

Please help me elaborate the list by posting your list of such features, such as those that you've already used as part of a user story management tool, or those that you'd like to see in the software tool you use. Do you find some features more important than the others? Many thanks in advance! 

Pages

AgileConnection is a TechWell community.

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