Hot answers tagged

18

Really good question. Really hard to answer. Here is my two cents contribution. Agile showed up as a response to the practices of the late nineties for building software, practices that assumed you could define everything upfront in such detail and plan them out such that it was then just a matter of following that plan to reach a successful outcome. But ...


14

TL;DR Trying to "future proof" your data is done by making your tools, processes, and data structures flexible, not by fixing them for eternity. You do this by embracing test-first database design, ensuring your data is normalized and extensible, and that your tools and processes support change. You do not accomplish this by treating your data or ...


10

The agile approach does not necessarily imply shortsightedness. Depending on the problem domain, you may have a very complete understanding (in your example, the industry exists for quite some time, has best practices, etc.) or a very limited understanding (such as a novel idea for a social network). Very complete understanding It would be foolish to throw ...


8

How should a PM reconcile the wish to deliver something quickly, which may require extensive rework to add functionality in the future, versus doing extensive design up front then being able to develop all of the functionality quickly thereafter, with minimal rework? This is the question at the heart of agile. You could rephrase the question as: Is the ...


1

Open source software for Scrum/Kanban Here are two open source options for software project manangement using Scrum/Kanban. Tuleap ALM: See the Explore Tuleap Community Edition section for more details. Taiga on-premise self-managed However: You need to pay for the hosting provider. You need in-house skills to install, operate and maintain these software.


1

I am assuming that the projects you are working on are small / medium Scrum projects. Google spreadsheets or Excel Office 365 (to enable online collaboration) could be an alternatives. You could google search for managing small/medium scrum projects using Google Spreadsheets templates(free) or MS Excel templates to be used with Office 365 for sharing(paid). ...


1

On Tuckman model, do teams using Agile frameworks mature faster in comparison to teams using Waterfall? Theoretically, yes. Practically, it's never that simple. You could think about the Tuckman model as a chemical reaction that the team needs to pass through and eventually reach a mature state in which the team performs at its best. And chemical reactions ...


1

The Tuckman model was solely based on observations made on teams. There is no comparison between the types of work, types of teams, industries, methodologies, framework and how any of those things might produce different results as a team matures. Also, I recall no discussion on how to "speed" up the maturity level and that these observed ...


1

I'm going to make an assumption that you mean Scrum. One of the common differences that you'll encounter as it relates to teams is that Scrum and some other frameworks and methodologies that fall under the Agile umbrella require or encourage long-lasting consistent, self-organizing teams. On the other hand, though it is not inherent in waterfall approaches, ...


1

It seems like this question is based on the misconception that decomposing a large feature into smaller units of work is a form of big design up-front. It's not. Big design up-front is designing the whole system, or at least large parts of a system, before starting any implementation and integration happens. Although decomposition is a design activity, it's ...


1

Scrum and its associated techniques don't eliminate the need for long-term planning but they can help make your planning and estimation tasks easier. If you deliver in fixed-length increments then your estimation only needs to be good enough to estimate the number of sprints a big ticket item will take rather than the number of days effort or duration. ...


1

It sounds to me like your very-small team also consists of, shall we say, "subject-matter specialists." And this might in the short run simply "be the hand that you've been dealt." But I think that you want to take every opportunity to emphasize that "we are all one team," and so, to the greatest extent possible, "we all ...


1

A really fun way is doing a Design Sprint. Followed by some Impact mapping and User story mapping. Depending on your product get out of the freaking building and let the developers talk to actual users. Maybe research the Shiftup program to help you facilitate continuous innovation. Bring the team together with the users and key-stakeholders, get and keep ...


Only top voted, non community-wiki answers of a minimum length are eligible